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 chart SLO repair without dropping current administrative guarantees

pulse-triage[bot]fbe410e244f3
diff --cc docs/release-control/v6/internal/subsystems/agent-lifecycle.md
index e8f16fca85,72d0ae8ce8..4c9051a0f3
--- a/docs/release-control/v6/internal/subsystems/agent-lifecycle.md
+++ b/docs/release-control/v6/internal/subsystems/agent-lifecycle.md
@@@ -10288,13 -10278,8 +10288,18 @@@ The actual CLI/receipt control i
`TestContractChartSLOProofCLIClassifiesExecution`; the separate read-only
evidence and check-writer boundary is
`TestChartSLOWorkflowPreservesInconclusiveAndFailure`.
+ Bounded hosted provisioning-agent CPU is now attributed separately, retaining
+ raw observations and enforcing the same 90 ms budget with that overhead present.
+ An over-budget run in this normal hosted envelope fails rather than disappearing
+ into neutral. Other/unattributed CPU and guest/steal/swap still invalidate the
+ timing. Neither verdict supplies any of the independent lifecycle proofs above.
+
+### Administrative JSON does not select agent operations (24 October 2026)
+
+The public SSO and RBAC administrative JSON admission rejects competing field
+values before settings, roles or one-use recovery tokens change. It exposes
+no agent enrollment, command, update or credential operation. Singleton
+requests and existing access, organization and Community SSO gates remain;
+`TestContractSSOAmbiguousSavePreservesDetail` and the SSO/RBAC JSON admission
+tests establish configuration/account preservation, not installed agent or
+guest recovery.
diff --cc docs/release-control/v6/internal/subsystems/api-contracts.md
index a2bf785014,c3540f1f41..da6e1cd397
--- a/docs/release-control/v6/internal/subsystems/api-contracts.md
+++ b/docs/release-control/v6/internal/subsystems/api-contracts.md
@@@ -12636,24 -12636,14 +12636,32 @@@ report, wrong budget, cleanup failure o
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
+ real CLI and disposable child processes through idle, hosted-agent and contended 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.
+ On actual Actions execution, one exactly named `provjobd<digits>` process may
+ account for at most one logical CPU plus one percentage point of sampling skew.
+ Only that bounded contribution is separated from competing CPU; all other
+ observed and unattributed CPU retains the 10% limit. Multiple or over-bound
+ agents, non-Actions execution, guest/steal and swap get no exception. Receipts
+ retain raw CPU rows plus runner-agent/competing attribution and CPU count.
+ The hosted overhead remains in the absolute latency: under-budget passes and
+ over-budget failures both receive real verdicts, without normalization.
+
+### Unambiguous public administrative writes (24 October 2026)
+
+Public SSO provider create/update and RBAC reset-admin require one complete,
+bounded JSON object. Competing members for a decoded request field, including
+escaped and case-folded aliases and repeated nested OIDC/SAML objects, return
+`400 invalid_json` before persistence, provider initialization, role changes or
+recovery-token consumption. Group-role map keys remain case-sensitive data;
+exact or escaped duplicates cannot choose a later role. Well-formed unknown
+fields and singleton aliases remain compatible. Deliberate empty restrictions,
+blank-secret preservation, Community SSO and existing tenant/access/licence
+checks are unchanged. SSO consumes the full 1 MiB bound; reset-admin retains
+its 4 KiB bound, including trailing whitespace. No route or response field is
+added. `TestContractSSOAmbiguousSavePreservesDetail` binds the error and retained
+detail response; `sso_json_admission_test.go`, `rbac_json_admission_test.go` and
+`admin_json_test.go` cover persisted preservation, explicit clears, aliases,
+limits and one-use recovery. These are public source controls, not an observed
+exploit, private runtime acceptance or installed sign-in recovery.
diff --cc docs/release-control/v6/internal/subsystems/storage-recovery.md
index e57c4e303f,8c2017e2ab..b7a63ca5e2
--- a/docs/release-control/v6/internal/subsystems/storage-recovery.md
+++ b/docs/release-control/v6/internal/subsystems/storage-recovery.md
@@@ -7249,14 -7249,8 +7249,19 @@@ History latency result, intact stored d
recovery. `TestContractChartSLOProofCLIClassifiesExecution` preserves child
exit, output and executable identity across those distinctions; the 90 ms
valid-capacity requirement and independent native recovery remain unchanged.
+ One bounded hosted provisioning agent is part of the absolute measured envelope,
+ not a blanket contention exemption: other/unattributed CPU, guest/steal and swap
+ remain invalidating. Raw CPU and agent attribution are both retained. This
+ permits a real failure as well as a pass at 90 ms; it clears no earlier adverse
+ timing, storage failure or excluded investigation and changes no store code.
+
+### Rejected administrative input preserves saved recovery choices (24 October 2026)
+
+Competing public SSO request fields cannot overwrite restrictions or saved
+provider credentials, and ambiguous reset-admin fields cannot consume the
+one-use token while selecting a different account. A complete unique request
+can still deliberately clear restrictions or perform its authorized scoped
+reset. `TestContractSSOAmbiguousSavePreservesDetail` and the SSO/RBAC JSON
+admission tests preserve persisted settings, exact roles and token usability.
+No database schema, stored history, backup/thaw operation or native recovery
+route changes; parser admission does not establish those operational outcomes.