Preserve resident memory and report checkpoint state accurately

[joelteply]

Resident startup now refuses a slot when persistent engram storage cannot be restored. It preserves the original OrmStoreError in SupervisorError::AdmissionRestore instead of continuing with an empty AdmissionState and NoopSink, which also lost future admissions. Existing residents remain registered, healthy sibling slots can continue, and a new home still initializes persistent storage normally.

Working-memory restoration now describes the checkpoint evidence accurately: its age is time since the save, pending dispatch labels carry unknown completion and side effects, and an empty list means no pending dispatches were recorded in that checkpoint. Missing or zero save timestamps remain unknown. Restoration no longer asserts an interruption time, noncompletion, or safety to repeat an operation. The snapshot schema and existing rebuilt notice are preserved; the Persona decides what to do next.

The bootstrap regression calls actual materialize_adapters with a non-SQLite candidate database, a healthy sibling, and both cold and already-registered cases. It checks the original storage error, unchanged corrupt bytes, healthy persistent initialization, and exact prior resident preservation. The existing working-memory roundtrip regression now checks truthful pending-state wording and missing/zero save timestamps while retaining memory, receipt-counter, and rebuilt-notice checks. The recovery guide also distinguishes persistent engram identity from checkpoint adoption.

Validation:

• At 901adbd, independent source reviews, rustfmt, and git diff --check passed. CI run 34288166852 passed 7,848 library tests, two compile-fail doctests, Windows library/test-harness checks, and binding checks.
• Dependency Preserve legacy Persona checkpoints and refuse blank recovery #3925 at b4e0060 separately passed 20 native Windows library/CLI tests and CI run 34286768088.
• Checkpoint-wording change 3908748 passed source review and git diff --check. Its CI run 34294103069 was cancelled when the combined head superseded it; it did not produce a completed validation result.
• Combined head 64703ce merges canary 8c088d2, including fix(cognition): preserve history corrections and result provenance #3923's speech/history/result-provenance fixes. CI run 34294884732 passed 7,848 library tests, two compile-fail doctests, Windows library/test-harness checks, and binding checks. Both the real admission-restore regression and the amended checkpoint-fact roundtrip passed at this head.
• Combined native Clippy at 64703ce exited 0 but emitted 1,356 warnings against a 1,351-warning baseline. This was not a clean Clippy result or merge-readiness receipt; subsequent warning corrections require fresh validation.
• Warning corrections are now included: c55720a carries Preserve legacy Persona checkpoints and refuse blank recovery #3925's checkpoint-adoption nonminimal_bool and CLI items_after_test_module fixes, and 7dd3bff checks the held-work fixture registration Result introduced by the fix(cognition): preserve history corrections and result provenance #3923 composition.
• The three mechanical lint corrections were source reviewed: the prescribed is_none_or equivalence, an unchanged helper block moved before the test module, and the checked registration Result. Clippy executed at 64703ce only; no post-fix native Clippy run is claimed or required for readiness.
• Corrected head 7dd3bff passed CI run 34296173747: 7,848 library tests (0 failed), both compile-fail doctests, Windows library/test-harness checks, and binding checks. The real admission-restore regression and amended checkpoint-fact roundtrip both passed. Dependency Preserve legacy Persona checkpoints and refuse blank recovery #3925 head 9d3fe80 also passed its fresh CI and merged as 70ec392.
• Current head 42f0a12 integrates canary after Preserve legacy Persona checkpoints and refuse blank recovery #3925's squash merge. It preserves the tested memory source from 7dd3bff; the only file differences are canary's README.md, core/llama/build.rs, and docs/planning/VIRAL-LAUNCH-PLAN.md. Its tree is 29b525b31c480f1be38db4b7ecf9dc5ea7ba3b58. Fresh CI run 34298594638 is in progress. No repeated native Clippy run is required or claimed. No deployment or memory database changes performed.

Dependency #3925 is merged. Fresh CI on 42f0a12 is the remaining execution gate. Card 6d17695c-a8a3-4df6-bd6e-b2172a41ee82.