Advance the immutable candidate after rc.7 failed its backend gate, keep stable rollback on v6.3.2, and refresh release, Docker, Helm, and mobile-compatibility metadata.
Change-source: pulse-maintainer
Prevent the idempotent poll test from cancelling the first request after the handler starts but before the service records a successful synchronization.
Change-source: pulse-maintainer
Package durable alert lifecycle recovery, richer scheduling and routing, capacity forecasting, host disk policy, external availability monitoring, and governed action verification for the next prerelease.
Change-source: pulse-maintainer
Recognize the focused offline mock host regression as monitoring runtime evidence and pin the canonical guard expectation.\n\nChange-source: pulse-maintainer
Serialize API-token disk reload snapshots with live token mutations so a stale watcher read cannot overwrite a newer rename or revoke. Add deterministic rename and revoke race coverage and record the governed concurrency boundary.
Change-source: pulse-maintainer
Include the focused alert-incident proof in the monitoring fixture policy expectation so the subsystem lookup unit test tracks the expanded registry.
Change-source: pulse-maintainer
Record the agent, performance, and storage boundaries for fixture-owned alert timelines. Teach the verification registry to accept the focused mock incident and alert transport proofs used by the implementation.
Change-source: pulse-maintainer
Add the canonical workload fallback to rolling CPU policy controls and show each profile's effective parent duration. Refresh stale alert and Ceph guardrail expectations found during full-suite validation.
Change-source: pulse-maintainer
Keep in-memory observations authoritative over duplicate persisted history, add direct provider and cache reset coverage, and register the rolling-window proof files with canonical governance.\n\nChange-source: pulse-maintainer
Extend the canonical completion guard's expected backend proof set with the focused Docker action tests admitted by the registry.
Change-source: pulse-maintainer
Recognize the focused Docker action API tests as backend payload proofs and record the explicit container-health boundary in the dependent storage/recovery contract.
Change-source: pulse-maintainer
Record the bootstrap-to-runtime credential replacement as one durable transition across API, agent lifecycle, security, and storage contracts. Document rollback, replay, and no-secret-on-failure guarantees proved by the deploy handler suite.\n\nChange-source: pulse-maintainer
Contract-Neutral: Implements the existing responsive DetailSectionTable contract for the remaining unified-resource drawer; no contract surface changes.
Richard Courtman