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.

Reconcile chart reporting with current Patrol contracts

pulse-triage[bot]7e7cea87a6bc
diff --cc docs/release-control/v6/internal/subsystems/agent-lifecycle.md
index 851351c588,f5088308d1..18ea7f5d6f
--- a/docs/release-control/v6/internal/subsystems/agent-lifecycle.md
+++ b/docs/release-control/v6/internal/subsystems/agent-lifecycle.md
@@@ -10211,7 -10211,14 +10211,19 @@@ inbox expiry sweep expires, enrols, com
touches no agent identity or credential. Investigations still reach hosts only
through the read-only evidence tools and the governed action lifecycle.
+The `internal/api` change of 2026-10-23 that serializes the projection of a
+Patrol investigation's action and finalizes Patrol runs that ran past their
+limit enrols, commands, updates or removes no agent and touches no agent
+identity or credential.
++
+ ### Hosted chart evidence cannot qualify an agent lifecycle
+
+ The optional hosted workload-chart capacity proof reports an executed but
+ contended measurement as inconclusive, never as a healthy reading or a passed
+ 90 ms budget. This CI-only classification does not satisfy agent installation,
+ restart, confinement, credential persistence or signed recovery acceptance.
+ Skips, missing reports and non-budget child failures still fail the proof.
+ The actual CLI/receipt control is
+ `TestContractChartSLOProofCLIClassifiesExecution`; the separate read-only
+ evidence and check-writer boundary is
+ `TestChartSLOWorkflowPreservesInconclusiveAndFailure`.
diff --cc docs/release-control/v6/internal/subsystems/api-contracts.md
index 42902431cd,bc80368ff6..a34c4c68b9
--- a/docs/release-control/v6/internal/subsystems/api-contracts.md
+++ b/docs/release-control/v6/internal/subsystems/api-contracts.md
@@@ -12564,17 -12564,16 +12564,31 @@@ changes. Proofs: `internal/actionlifecy
`internal/api/patrol_action_expiry_sweep_test.go` and
`internal/api/ai_handlers_investigation_finalize_test.go`.
+### Field-level action writes and serialized Patrol action projection (23 October 2026)
+
+`aicontracts.InvestigationActionStore` is a new optional interface on the
+Pulse–enterprise boundary: an investigation store that offers
+`SetAction(id, action)` lets Pulse record an action lifecycle transition
+without replacing the session. Pulse's Patrol action projection uses it with
+`SetOutcome` when the store offers it and falls back to `Update` for a store
+without it, so an older store keeps working. Projections of one investigation,
+and a run's close, are serialized under that investigation's lock. The
+investigation's action reference now includes `action_result_v2` and
+`verification_status`, the projection the broker's disposition already
+carries, and keeps `causal_resource_id` for the same action, so investigation
+payloads may carry these optional fields where they were empty before. No route
+changes. Proof: `internal/api/ai_handlers_investigation_additional_test.go`.
++
+ ### Workload-chart proof distinguishes an invalid measurement from recovery
+
+ `internal/api/testdata/chart_latency_proof.py` keeps the strict 90 ms budget,
+ exact one-test execution, executable digest and child result in its receipt.
+ Only a single complete PASS or budget-only FAIL with competing capacity can
+ exit 78 and describe the timing as inconclusive. A skipped/missing/duplicate
+ report, wrong budget, cleanup failure or other child failure remains an error.
+ A valid-capacity budget failure still fails. No API payload, route, History
+ sample, incident state or operational-recovery result is changed by this CI
+ classification. `TestContractChartSLOProofCLIClassifiesExecution` drives the
+ real CLI and disposable child processes through all ten outcomes, verifies
+ unaltered logs/result/digest/strict arguments and excludes the synthetic token
+ from the child environment. Its capacity rows are synthetic, not latency proof.
diff --cc docs/release-control/v6/internal/subsystems/storage-recovery.md
index 6ace2052ed,577269a91c..bc0fcaf345
--- a/docs/release-control/v6/internal/subsystems/storage-recovery.md
+++ b/docs/release-control/v6/internal/subsystems/storage-recovery.md
@@@ -7199,6 -7199,13 +7199,17 @@@ runs when they close and publishes the
expires opens no storage, backup or recovery path. Recovery evidence, restore
rules and storage capabilities are unchanged.
+The `internal/api` change of 2026-10-23 that serializes the projection of a
+Patrol investigation's action and finalizes Patrol runs that ran past their
+limit opens no storage, backup or recovery path.
++
+ ### Capacity-invalid chart evidence is not storage recovery
+
+ The hosted workload-chart proof may call a complete, contended measurement
+ inconclusive without clearing its raw budget failure. It must not turn a
+ cleanup/child error, absent report or skipped test into neutral evidence.
+ Neither neutrality nor synthetic CLI classification establishes a valid
+ History latency result, intact stored data, guest liveness or installed
+ recovery. `TestContractChartSLOProofCLIClassifiesExecution` preserves child
+ exit, output and executable identity across those distinctions; the 90 ms
+ valid-capacity requirement and independent native recovery remain unchanged.