fix(runtime): archive retired dependency rebind before restore

[roodboi]

A completed dependency-rebind journal from a prior guest boot can survive absent-publication cleanup and cause a later retained restore to withhold every routed endpoint. Archive that journal before a new foreground restore, using its exact original ready generation, exact historical stopped completion and durable retirement proof.

Archive writes and renames recheck the held foreground lock, provider/boot identity, both generations of absent compute, retained volume projections and cache-witness linkage. Original journal bytes remain in the existing digest-bound archive; interrupted renames resume against the same proof. Current-boot journals, changed evidence and pending or live resources refuse historical archival. Future absence cleanup performs the same retirement after publishing its completion proof.

This branch includes the retained recovery stack from #103–#105 and #110–#111, and reconciles it with current next. It remains a draft pending integrated CI and actual application acceptance.

Validation: regressions for exact historical completion, changed boot/generation, replaced foreground lock, lost ownership before archival, interrupted rename, substituted archive proof and cache-witness cleanup linkage. Before reconciliation: default Rust suite 971 passed / 62 ignored; all features 1057 passed / 84 ignored; both Clippy configurations and staged privacy scan passed. Integrated gates and signed retained-application startup are in progress. Ignored host fixtures and browser acceptance are not represented as passes.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[roodboi]

Superseded by merged #122. This PR’s source was incorporated through #122, squash commit cf4b6e9. Independent acceptance remains in Linear. Closing as superseded; branches and worktrees are retained.