mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-25 21:20:00 +00:00
pulse-triage[bot]
f20d5cdfbb
**Keep canonical protection aligned with recognised Proxmox subjects** Use the same subject normalisation as recovery rollups when deriving protection. Fresh points carrying recognised legacy node-scoped identities must not disappear from a canonical guest's posture. Cover stale-plus-fresh histories, incomplete/running/task evidence, independent estates and the real poll/async-ingest path. This does not establish the cause of issue #3248. **Publish the canonical subject in persisted protection posture** The real poll regression caught a second identity boundary: selecting the newest point's raw subject still made canonical reads miss the derived posture. Reuse recovery's recognised subject resolver for the persisted projection, and verify both canonical requested reads and state-filtered lists. No schema, driver, policy or identity resolver change. --- Fleet candidate `20261025T100027Z-core-runtime` from the `core-runtime` lane. Reviewed tip `b0d76d7cea27f9d612e365809e3147e11383aa06` on `main`. [How Pulse handles triage](https://github.com/rcourtman/Pulse/blob/main/docs/AI_TRANSPARENCY.md)