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 scoped agent disclosure repair with current main

pulse-triage[bot]7fed427a939c
diff --cc docs/release-control/v6/internal/subsystems/storage-recovery.md
index 6b4098c097,322515d99c..78a99a42fc
--- a/docs/release-control/v6/internal/subsystems/storage-recovery.md
+++ b/docs/release-control/v6/internal/subsystems/storage-recovery.md
@@@ -21,30 -21,22 +21,46 @@@
## Purpose
+### Coverage provider outcomes are not backup job results
+
+Provider evidence identifies the source of each scoped assessment: PBS/PVE
+backup inventories have explicit names; legacy restore-point evidence is named
+as such, and unrecognised sources remain literal text (or Unknown when absent).
+The rollup's `jobState` is displayed as Reported outcome, never Job or Collection:
+an inventory observation can supply it, but a newer retained point can also
+supply the outcome beside an older observation's source. Visible wrapping copy
+keeps this evidence distinct from actual task and restore-point states. History,
+access, reported values, protection, dates and policy do not change. The shipped
+PBS/PVE comparison guides name the same Source/Reported outcome fields and
+keep successful inventory reads separate from backup-task completion. Rendered
+help tests preserve this distinction and every original-recovery safety limit.
+
+Normal-suite `ProxmoxCoverageTable.test.tsx` covers known/unknown/literal sources,
+all reported outcomes and narrow/wide rendering. `ProxmoxBackupsTable.test.tsx`
+passes parsed inventory and posture reads through the consuming surface,
+retaining a Running/unprotected point and a real OK task independently of
+successful or failed inventory evidence, including polling and owned focus.
+Desktop/narrow browser proof must inspect the production Backups consumer with
+source-bound collector frames, its separate task/evidence meanings and readable
+source/outcome/qualifier. This is safer inspection, not backup-job execution,
+original guest recovery, a tested restore or published availability.
+
+ ### Scoped agent outcome reads do not disclose execution detail
+
+ The agent event/resource-context projections preserve validated execution,
+ verification/evidence-class and compensation axes in an explicitly redacted
+ `actionResultSummary` for tokens without `ai:execute`. Full canonical evidence,
+ free-form result/error text and verification notes are withheld rather than
+ rewritten into new evidence. Known refusal prefixes remain branchable; session
+ and existing command-capable reads remain unchanged. No stored evidence, agent
+ command admission, recovery action or recovery-data identity changes.
+
+ The ordinary API disclosure/contract tests check legacy and V2 producers,
+ malformed-digest fallback, stored-evidence preservation and scoped concurrent
+ streams. The MCP consumer test checks real authenticated tools/call and live
+ notification readback. A content-free outcome is not independent recovery proof
+ or permission to replay any stopped operation.
+
### Datastore discovery cannot turn unread history into absence
PBS datastore enumeration uses the same bounded, fully read and closed HTTP 200