Skip to content

armgit / Pulse

Public Imported from GitHub
0

Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.

Compose task-history safety without dropping the memory contract

pulse-triage[bot]0ffcd5943641
diff --cc docs/release-control/v6/internal/subsystems/storage-recovery.md
index ed397455bc,cf23f4c56c..c48f132ce3
--- a/docs/release-control/v6/internal/subsystems/storage-recovery.md
+++ b/docs/release-control/v6/internal/subsystems/storage-recovery.md
@@@ -21,29 -21,36 +21,59 @@@
## Purpose
+### Backup-server memory does not invent empty or current readings
+
+The Backup servers table keeps a valid selected memory percentage when a partial
+metric reports capacity without used bytes; it never substitutes zero used bytes.
+A displayed byte pair needs finite non-negative used bytes and positive capacity,
+with used not exceeding capacity. Valid reported pairs still determine the
+percentage, including an explicit measured zero. An independent finite percentage
+in the range 0–100 remains usable when the byte pair is absent or invalid.
+
+Server reachability does not renew memory evidence. The table reuses the resource
+drawer's memory-observation qualification: retained and unknown readings say
+`Last known` or `Freshness unknown`; explicitly unavailable readings show no
+number. A stopped linked agent qualifies its own reading without invalidating an
+independent current source. Offline suppression, datastore risk, backup counts,
+identity, History targets and original observation clocks remain unchanged.
+
+Normal-suite `ProxmoxBackupServersTable.memory.test.tsx` covers partial and invalid
+metrics, measured zero, retained/unavailable/future observations, stopped-agent
+source isolation, live recovery and multi-datastore/offline controls. Browser
+proof must consume the resource producer through the actual Backups surface and
+its existing drawer at desktop and narrow widths. This improves truthful
+inspection, not installed memory relief, a successful backup or guest recovery.
+
+ ### Unread PVE task history cannot establish absence or completion
+
+ The paginated backup-history collector admits only a complete, bounded HTTP200
+ response with an explicit task array and unambiguous, scoped task identities and
+ times. Missing/null inventories, duplicate or case-conflicting fields, invalid
+ rows, contradictory errors, trailing data and unfinished bodies are unread,
+ not empty history. Audit authority likewise requires a whole unambiguous
+ response granting `Sys.Audit` on the requested node; a valid prefix cannot
+ qualify collection completeness. Valid empty arrays, independent accepted pages,
+ provider metadata, multi-guest jobs and existing pagination bounds remain valid.
+
+ Live tasks on a transiently unread/offline node retain only their last accepted
+ connection-scoped observations. Accepted IDs win, other nodes still advance, and
+ carried rows neither renew `ObservedAt` nor re-enter durable ingestion. Accepted
+ empty reads and removed nodes withdraw their live rows. Explicit access denial
+ withdraws that node's live rows and accepted page prefix; a later failed read
+ cannot resurrect them. History coverage remains incomplete until its existing
+ collection/authority checks pass. Retained running intent continues to keep its
+ writer's partial archive from claiming completion. No new endpoint, field, token
+ scope, policy, store/schema migration or guest/backup operation is introduced.
+
+ Normal-suite `backup_history_response_test.go` covers adverse envelopes, rows,
+ body completion, audit evidence and later-page failures; pagination controls
+ remain required. `backup_task_inventory_lifecycle_test.go` exercises the actual
+ HTTP client and poller through unread/empty/recovery/denial, connection isolation,
+ fresh-page precedence and VM/LXC partial-archive ingestion. Desktop/narrow browser
+ proof consumes those actual task frames in the production Backups table. These
+ are source continuity and attribution proofs, not restore availability, original
+ guest recovery or the cause of a reported freeze or stale date.
+
### Fleet protection reads bound their request fan-out
Coverage reads keep the existing 200-subject batch size and issue at most four