v1.19.0 — crash-dead capture alarm + ADR status derivation
- #283 crash-dead capture alarm (PR #291):
/api/statscapture entries gaincheckpoint_abstained_7d+last_turn_day; um-alert gains the fifth section CRASH-DEAD — pages when a surface that used to post turns goes silent while session-end keeps stamping abstained checkpoints (the one silent-death class no deployed instrument could see). Post-deploy live-fire verified on the Pi. - #275 ADR status derivation (PR #290):
adr_statusnow derives the server-managed point status on the identity path — retired ADRs leave default recall (include_superseded=truerecovers them); un-suppression = flip frontmatter + re-sync. Live-verified: ADR-0004 gone from default search post-sync. - #285 (PR #288):
create-adr.shgains the~/.um/auth-tokenfile tier — bare/adr syncauths on hooks-configured machines. - #286: append-turn field-validates before the F1 soft-default — no more warn-then-400 log pairs from the healthy G7 probe.
- Test hygiene: #289 (reaction-ledger fixture clock un-pinned).
Deploy notes: refresh the installed CLI (install-cli.sh) with the server swap — the um-alert cron copy needs it for the new section (the #283 checklist's step 0 verifies).