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 retained scoped-read repair with current main

pulse-triage[bot]0d39a9dbb89e
diff --cc docs/release-control/v6/internal/subsystems/storage-recovery.md
index 58c80b2288,b6400ae922..cb8b744043
--- a/docs/release-control/v6/internal/subsystems/storage-recovery.md
+++ b/docs/release-control/v6/internal/subsystems/storage-recovery.md
@@@ -21,42 -21,38 +21,74 @@@
## Purpose
+### Backup views share bounded owned-focus restoration
+
+Coverage posture sorting and By date regrouping use the same existing backups
+presentation helper for focus lost during a retained native DOM move. It restores
+only the same connected target still inside its table and cancels after any
+intervening focus choice, even if that choice is later blurred. By date's earlier
+restoration did not cancel that latter choice; its normal-suite date-group
+regression now covers it. Genuine retirement still uses the existing surface
+fallback. No sorting, date validity, collection, protection or access rule changes.
+The consolidation reduces overlapping handling. Its exact build still exceeds
+the August Proxmox reference budget by 0.07 KiB; the final candidate declares a
+bounded 256-byte Proxmox reference allowance (80,595 → 80,851), not a measured
+baseline reset. The 15% threshold, every other chunk and total limits remain
+unchanged. Normal Proxmox/shared suites and exact production checks verify it.
+Desktop/narrow actual Backups proof includes both views and source-bound pixels.
+
+### Coverage retains owned focus when live posture sorting moves a row
+
+An accepted posture or inventory frame can reorder the same logical workload.
+Keyed row/component retention alone does not retain native focus when DOM nodes
+move. Coverage captures a focus target owned by its table before reconciliation
+and restores that same element without scrolling only if the completed move
+leaves BODY focused and the element and table remain connected. An intervening
+focus choice cancels restoration, even if that choice is subsequently blurred.
+External search/header focus is not reclaimed; removed or departed elements are
+not resurrected. Existing retirement fallbacks still own genuinely removed
+inspection content. Sorting, window budgets, row identity, drawer state,
+posture meanings, read cadence, policy and mutation permissions do not change.
+
+Normal-suite `ProxmoxCoverageTable.test.tsx` covers reordered VM/LXC disclosures
+at wide/narrow widths, retained detail links, external/intervening focus and
+retired/departed targets. Production Backups desktop Chromium and 320px WebKit
+proof binds actual poll-driven quality changes to unchanged same-node controls,
+contrasts the parent native focus loss and checks keyboard/touch use, sorting,
+filter retirement and no focus theft. This is inspection usability, not evidence
+of original workload recovery or a guest/provider operation.
+ ### Public-URL token checks share authentication ownership
+
+ The pre-route public-URL authority check uses the existing locked token
+ validator and detached snapshot. Normalisation and last-used metadata updates
+ hold the same exclusive configuration ownership as ordinary authentication;
+ subsequent scope checks never mutate the live record outside it. Both supported
+ token headers retain the existing settings-write requirement. Expired, invalid,
+ wrong-role and monitoring-only credentials gain no capture authority. Sessions,
+ proxy/basic administration and URL/origin selection are unchanged.
+
+ `TestPublicURLTokenCaptureUsesAuthenticationOwnership` covers concurrent capture
+ and ordinary authentication, retained scope/identity and successful last-use
+ updates; `TestPublicURLTokenCapturePreservesTokenRefusals` pins both headers and
+ refused metadata. The real concurrent history HTTP test remains unchanged and
+ must pass with the race detector; the observed race is not warmed away or
+ suppressed. No new rendered state, token grant or runtime action is introduced.
+
+
+ ### Execution history uses a typed read-only projection
+
+ The recent-change read keeps kind-specific scalar status facts, not arbitrary
+ caller metadata that happens to use a familiar key. Runbook titles, stored
+ reason/From/To text and nested values can contain execution details and are
+ redacted for monitoring-read callers. Fixed reasons derive only from admitted
+ boolean command success or the closed incident outcomes; missing or malformed
+ facts do not establish success or failure. Every execution-history projection
+ is explicitly marked redacted. Executor/session reads and canonical evidence
+ are unchanged; this adds no enrollment, token scope or action authority.
+
+ Normal-suite typed-fact, authenticated concurrent HTTP, contract and real MCP
+ consumer regressions cover content visibility and unchanged stored evidence.
+
### Coverage provider outcomes are not backup job results