catch-up session 2026-10-05: design 07 §6.1.1 (a box that is not always on), 08 §6.4; rulings 109-111, CC decisions 112-118; R-871/R-873..R-877 closed, R-872 narrowed (dated check), R-878 opened; live evidence; STATUS

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

documentation/architecture/11-os-updates.md

@@ -639,6 +639,19 @@ Agent v0.144.0 + v0.144.1 (wrapper and agent; `09` decisions 106–108). Evidenc
   (runbook `crash-guard.md`), then the next pass installed the 12. Operator mail `os_update_failed` (true); no
   household mail; the household's timeline showed "Controller elindult".
 
+### 8.5 The self-repair after a power cut as BUILT (2026-10-05, agent v0.145.0)  `[FACT]`
+
+- **R-876 fixed.** The wrapper reads `dpkg --audit` AND dpkg's update journal (`/var/lib/dpkg/updates/`) in ONE call
+  and repairs when either shows something; as a belt, when apt itself says "dpkg was interrupted", it repairs and
+  retries once (`09` decision 118). A clean pass still costs one call (R-845's speed, pinned by a test).
+- **Proven live** (operator's go, demo-hp, `audits/catchup-2026-10-05/partD/`): 13 guest packages rolled back, crash
+  at 07:56:03 UTC during dpkg's unpack, back by itself (new boot 07:56:41, guard armed, 1 unclean boot in the window);
+  at boot `--audit` clean, journal 1 file, the same shape as §8.4. **The next pass, with nobody touching the box:**
+  `REPAIR configured=0 journal=1`, then `DONE rc=0 upgraded=12`, healthy; the guest's package list equals the one
+  before the rollback. No mail (the pass did not fail); the household's timeline: "Controller elindult".
+- **R-874.** The agent's restore-test due-check runs 30 minutes after start (then every interval), so a box with short
+  power-on sessions is restore-tested (`09` decision 117).
+
 ## 9. Where the rest lives
 
 - The finding: **R-812** (`backlog/OPEN-ITEMS.md`). The intention: **R-808** (`backlog/ROADMAP.md`).