night 2026-10-23 so far: D30 live proof (re-key → new-key handshake; ep0-started handshakes heal a short clock jump by themselves), D4 patches v2 after review, test-night install/fixture evidence, DooPlex survival survey (read only) + PLAN, 03/05/07 + CONTEXT, total-loss runbook: MAIL-HOLD shipped

documentation/runbooks/total-loss-of-dooplex.md

@@ -69,7 +69,7 @@ local restic repos; Prometheus history; DooPlex's other homelab apps (not Felhom
 7. **Gitea:** `gitea-restore.md` (on a normal network this time). Then rebuild the images from the code into the new
    registry: hub, controller, agent (`RUNBOOK-manual-build.md`).
 8. **The hub:** k3s, then `RUNBOOK-hub-db-offsite-backup.md` §3 with S2 and S4 — **start it with mail held**
-   (§3 step 1: the `MAIL-HOLD` marker, from the next hub release; until then: no network until the pending notices are understood).
+   (§3 step 1: the `MAIL-HOLD` marker — shipped in hub 0.145.0, 2026-10-10).
 9. **DNS:** in Cloudflare (S11) point `hub.felhom.eu` (today a CNAME to `dooplex.hopto.org`) and `gitea.dooplex.hu` at
    the new place. The boxes reconnect by themselves: their API keys are in the restored hub DB.
 10. **Signing:** the keys are in the restored copy (`signing/`) and on the sheet (S6) — put them back and sign as before. Without it, no box accepts an agent update or a