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 accepted backup evidence repair with current main

pulse-triage[bot]6c51e8abdf9a
diff --cc docs/release-control/v6/internal/subsystems/storage-recovery.md
index 84d6fd037b,5b83946a55..155479ea4d
--- a/docs/release-control/v6/internal/subsystems/storage-recovery.md
+++ b/docs/release-control/v6/internal/subsystems/storage-recovery.md
@@@ -21,43 -21,37 +21,74 @@@
## Purpose
+### Backup-server read states remain legible at intermediate widths
+
+The existing PBS server table reserves enough count-column width for the full
+Loading and Unavailable labels, not only numeric counts, at basic, operational
+and expanded container widths. The shared 30% basic identity anchor, visible
+columns, 32px scan rhythm, independent connection/capacity evidence and full
+layout remain unchanged. Datastore names keep their existing truncation, title
+and detail access; no identity, count, polling, read/retry or protection rule
+changes. An unread inventory still never establishes a real zero.
+
+Normal-suite `proxmoxBackupsTablePresentation.test.ts` verifies width allocation
+and complete column totals; the registered `ProxmoxBackupsTable.test.tsx`
+exercises actual loading/failure/accepted-empty cells with independent healthy
+capacity. Browser proof must inspect the consuming table at desktop, phone and
+intermediate container boundaries, including loading, failure, retry, real zero,
+ordinary polling and native detail interactions. This is readable inspection,
+not installed or original guest recovery.
+
+### PBS server counts belong to the exact backup reader and datastore
+
+The existing Backups server count matches `PBSBackup.instance` to the resource's
+configured connection `name` and matches the exact datastore name. Service IDs
+(`pbs-` plus the connection name), hostnames and display labels are not backup
+reader aliases; an empty tuple must not borrow another connection's inventory.
+Both identities retain their positions, punctuation and case without a joined
+separator key. Counts still include all admitted inventory entries and namespaces,
+not only completed or verified points. Loading/unavailable inventory remains
+non-numeric; independently observed capacity and reachability remain unchanged.
+
+Normal-suite `backupServerCountEvidence.test.tsx` consumes parsed inventory and
+checks prefix-alias and delimiter collisions, case, namespaces, valid zero and
+existing all-entry semantics. Its real table consumer checks ordinary polling,
+failed reads, retry and detail continuity without extra requests. Desktop and
+narrow browser proof exercises the same producer through the inventory consumer
+with native interactions and inspected pixels. No API, provider, guest, polling,
+auth, resource identity or protection-policy change, nor installed recovery claim.
+
+ ### Accepted storage listings survive a later child-budget timeout
+
+ PVE storage polling commits listings accepted before a later node, content,
+ retry-wait or assignment read exhausts the child budget. A nil-error response
+ returned after expiry is unread, not a successful empty listing. No queued
+ provider read starts after expiry. Remaining known local repositories and
+ unlisted nodes retain their last live rows without renewing durable evidence;
+ only accepted rows advance. An accepted empty repository can remove its raw
+ rows, but incomplete instance-wide history cannot reconcile durable absence or
+ claim complete protection or clear an earlier access warning. PBS attribution without node provenance survives an
+ unread node until an accepted storage or complete enumeration replaces it.
+
+ Explicit request cancellation withdraws the enumeration. Dropping an expired
+ child deadline for local publication does not drop the connection owner:
+ runtime shutdown/replacement, client replacement and retirement still prevent
+ late publication. Unexpired publication retains its request cancellation signal.
+ A spent collection budget is not a recovery-store read failure: it does not
+ start an already-expired backup-alert read, invent an evaluation-outage warning
+ or clear existing wanted alerts. The next ordinary evaluation remains unchanged.
+ Independent connections, local-disk identity, permissions, guest operations and
+ provider budgets are unchanged. Every node's
+ ordinary storage reads remain; an accepted shared view is not substituted for
+ another node's access evidence.
+
+ `pve_storage_budget_test.go` covers VM/LXC, warm/cold live inventory, all five
+ expiry phases, exact retained/advanced raw and durable fields, accepted empty
+ membership, ordinary complete recovery, PBS attribution and owner withdrawal.
+ Source-bound desktop/narrow browser proof consumes emitted inventory/posture
+ frames through the existing Backups surface; this is not original installed
+ or frozen-guest recovery.
+
### Coverage duration requires observed task timing
The existing Coverage task disclosure derives a duration only from positive,