# REPORT — 2026-10-08 (day): six parts, tonight's kernel night untouched

(Written as `REPORT-day-2026-10-08.md` because another session worked in this clone today — the website refresh.)

| Part | Result |
|---|---|
| **A** — a daytime press never cancels the night (R-899) | **Done on main, ships tomorrow.** Controller `6d07ca2` (ledger; red-proved), agent `4c69c25` (no OS leg after a press; the "ring 1" label fixed). The household "tonight" mail case is removed by the rule; no hub change needed. |
| **B** — the old recovery code (R-304) | **Honesty fix done on main, ships tomorrow** — but in the agent (`91b9405`) and the controller (`75b3b39`), not the hub: the hub never sees the code (zero-knowledge), so it cannot check a row; it already reports what it withheld. Design with two questions: `documentation/audits/day-2026-10-08/design-R-304.md`. |
| **C** — alarm when a box never backs up off-site (R-243) | **Done on hub main `b119301c`, ships tomorrow.** 7 days (decision 179). Will fire once for Tester 2 after the deploy. `08` §6.3 updated. |
| **D** — wger's real web server (R-762) | **Half done.** Bench: 2 workers, 43–44 % memory, 0 kills, 0 restarts in 10 min, login/CSS/photo 200. **9202 not done:** the drill-catalog write was refused by the permission check; nothing pushed. No ladder step applies (same images). |
| **E** — legal drafts (R-813) | **Done, not published.** `documentation/legal/`: ÁSZF, privacy notice, imprint, consent text; 98 placeholders, 20 guesses listed. Two findings filed (R-900, R-901). |
| **F** — DooPlex backup failure mail (R-232 a) | **Done with your yes.** One test mail reached the inbox; no backup started. `documentation/audits/day-2026-10-08/r232/`. |

**Rows: 127 before → 130 after. Opened 2 (R-900, R-901). Closed 0.** (The third new row, R-902, is the parallel
website session's.)

**Waits for tomorrow's releases:**
- **controller:** R-899 (ledger, `trigger=manual`), R-304 (424 → "we do not know", hu + en). MinAgent unchanged.
- **agent:** R-899 (no OS leg after a press; after-boot ring label), R-304 (424 `older_unchecked`). Binary only.
- **hub:** R-243 `offsite_escrow_pending` (expect one Tester 2 mail).
- **catalog:** nothing (Part D not pushed).

**Operator rulings recorded first** (`09` §3): 177 (R-899 option A), 178 (today: no touch of the kernel night). CC's
pick: 179 (R-243's 7-day line — operator may reverse).

**Machines:** demo-hp, demo-felhom, Tester 1: read only (two log/state reads on demo-hp). Bench 9401: started and
stopped again by the Part D helper; its project removed. 9202: read only. DooPlex: Part F only (one script, one key file).
Hub: read only (a copy of its database, with the `-wal`, read and deleted). No release, no deploy, no reboot, no prune.

**CI (by head commit):** controller 1528, 1531; agent 1529, 1530; felhom.eu 1532 — all success.

**Seen, not fixed:** the recovery screen's 14 older messages are Hungarian-only (appended to R-516). A side note from
Part D: 9202's `recipe-importer` was removed by something else between 08:0x and 08:35 — not by this session.

## Decisions for you

1. **Part D on 9202 — may CC write to the shared drill catalog** (bring it up to date, un-hide wger there, point 9202 at
   it), as the 2026-10-06 sessions did? **My pick: yes** — it is a test catalog, and wger stays hidden on the real one.
   *If you do nothing:* wger keeps the slower development server, and it stays hidden.
2. **R-304 — keep the promise "old backups stay recoverable" as worded, and add an operator mail when a household's
   code opens an old package?** **My pick: yes to the mail** (small; it makes "contact support" true in practice).
   *If you do nothing:* nothing is built; you hear only when a household writes to you.