REPORT: the second burn-down night

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

REPORT.md

@@ -1,16 +1,16 @@
-# REPORT — v0.301.0: one stop per backup tier, restore order, the family window reopens (2026-10-06 evening)
+# REPORT — the second burn-down night (2026-10-06 → 07): three changes on main, unreleased
 
-MinAgent 0.131.0 (unchanged). The full session report, with the measurements, is `felhom.eu/REPORT.md`; evidence
+Nothing was released or delivered (brief fence); MinAgent stays 0.131.0. They ship with the next controller release.
-`felhom.eu/documentation/audits/design-build-2026-10-06/`.
+Session report: `felhom.eu/REPORT-night-burndown-2026-10-06.md`; night log
+`felhom.eu/documentation/audits/night-burndown-2026-10-06/NIGHT-LOG.md`.
 
-- **R-518** (`09` §3 decision 156, reverses R-82's one window): a window runs only the first due tier and resumes the
+- **R-542** (`f65ace0`): `/api/disks/candidates` drops every drive backing a registered storage path from „initialize"
-  apps at its `snapshotted`; the next tier waits for a later cycle; „Mentés most" makes the local copy only (none, and no
+  and „attach" (joined through the guest mount table; an unreadable table empties „initialize"). Two red-proofs.
-  stop, when the local storage is absent). Red-proved. **Not shown live** — the first night runs on the demo boxes are
+- **R-516** (`3d6ba28`): 22 Go-literal messages (escrow, share password, export upload, network storage) move into the
-  the proof owed (R-518 stays open).
+  bundle, the 14 formal ones in the te-form, with English; a detached NAS attach failure renders in the reader's language.
-- **R-638** (decision 154): the no-manifest fallback replays before the app starts; a failed volume leg skips the replay.
+- **R-330, wire only** (`1de22a1`): `SmartSummary` decodes SMART 187/188/199; carried only — no verdict change (pinned).
-  The main paths were measured safe on 9202 first (docmost, romm). Red-proved. Known limit: the off-site rollback's
+- Rows looked at and stopped: R-554 (the household's recovery file names the wizard — operator), R-562 (number/date
-  reverse direction (R-893).
+  format — operator), R-724 (needs an agent route — design), R-893 (which state after a failed off-site replay — design
-- **R-717**: `after_setup` `open_command` / `open_success`; proven live on 9202 with wishlist. Six red-proofs.
+  + operator).
-- Delivered: image `sha256:0e80f6af…`, golden 0.301.0 `96e94fed…`, floors 0.301.0 for demo-hp, demo-felhom, tester-1 —
+- Suite `go test ./...` rc 0; `controller/scripts/controller_gates.py` OK (golden-notice advisory); CI green (runs 1455,
-  all three run it. CI: `0b1b8d3` → 1439 success.
+  1463, 1466).
-- Not built: R-528 (its measurement contradicted the design — Docker 29.8.2 sets `OOMKilled` correctly).