mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-26 05:29:45 +00:00
9fb404604b
Improvement: backup-age false-recovery repair now has executable and desktop/phone pixel proof. **Continuation — truthful monitoring and backup evidence.** Candidate **6fb43d9302d6673bc65193f3e17944098394ad6d**, above **c67f8bd500**, contains **208f0cbf1e** plus an additive fixture correction. Original-runtime control reproduces false recovery; full alert race/vet, final consumer type checks, **1,404 tests**, compiled real Overview and both browser journeys pass. Complete output hashes match, source guests stopped, and all eight captures were natively opened and inspected. Coordinator/reviewer/publisher own containing CI, independent review and landing; their containing result or repair return is next. **Not landed, released or installed recovery.** [Receipts](RECEIPTS.md), [source](SOURCE.json), [continuation](CONTINUATION.json). This raises the highest-ranked **guest/backup safety** weakness: a still-listed backup's missing/zero/future date no longer clears an established warning or hides valid provider evidence. Last trusted occurrence/evidence survives; valid recent success, exclusions and authoritative removal still clear normally. The executed baseline establishes the defect, not a field incident's cause or native thaw safety. [Reproduction](REPRODUCTION.json), [scope and original jobs](RECONCILIATION.json). The first consumer proof exposed a fixture-only type error; the additive correction uses the current AI capability store without changing production code or weakening checks. Both commits pass canonical preflight; the frontend-file guard skip is not the separately completed browser proof. [Validation](VALIDATION.json), [adverse evidence](ADVERSE.json), [pixels](PIXEL-REVIEW.json). Received continuations **416bb1c9 / 58e731f1** are completed at the source-validation step. Previous node candidate **3c66ab14e7** and Delivery/Pro/Host/PI's original installed guest, dashboard, SSO and notification recoveries remain separately retained. No duplicate handoff, infrastructure, guest probe, excluded investigation, release or public action. --- Fleet candidate `20261023T172026Z-core-runtime` from the `core-runtime` lane. Reviewed tip `6fb43d9302d6673bc65193f3e17944098394ad6d` on `main`. [How Pulse handles triage](https://github.com/rcourtman/Pulse/blob/main/docs/AI_TRANSPARENCY.md)