chaos-night fixes: R-539 closed PROVEN-LIVE, the morning note, the report

R-539 closed: five real controller kills on demo-hp 9201 with the production
24 h window raised controller_slow_crashloop, and exactly one operator mail
arrived (09:29:40Z). The fast brake never armed.

Register 215 -> 213 open (R-551, R-552 filed; R-539, R-546, R-549, R-550 closed).
unproven.py: 35 of 55 not walked, no number moved.

The report names the brief's wrong claims first and one recommendation not
followed: the controller floor was not raised - validated on one guest, a gap
of my own found during validation, and a floor above the golden reaches Peti's
box too. The operator's call.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

STATUS.md

@@ -1,5 +1,46 @@
 # STATUS — what works, what's broken, what's next
 
+**Updated 2026-09-17 (midday) — the four things chaos night found are fixed, and three of them were proven on the demo box.**
+
+> **Ready for a volunteer: yes.** Nothing here was blocking; all four made the box more honest or less
+> noisy. The recruiting sentence: *if the power fails in the middle of a restore, the box now says so and
+> tells you to run it again; and it no longer asks for the recovery code before it can take it.*
+
+**Decisions I took.** None under the unattended rule. I carried out your three rulings: the quiet-box
+alarm waits three report cycles; the restore record is kept on disk; the slow crash-loop warning. I
+signed the agent update onto the two demo boxes under yesterday's ruling.
+
+**What I exercised, on real boxes.**
+- The hub now waits **45 minutes** before „the box went quiet" and **90** before „the box is down". The
+  running hub prints both numbers when it starts. A dead box now pages you 15 minutes later — your
+  ruling's accepted cost.
+- I started a restore on the demo box and killed the controller **two seconds** in. It came back by
+  itself. The restore page then said „A visszaállítás megszakadt — indítsd el újra", and the hub got the
+  event. Restoring again cleared the note.
+- I killed the demo box's controller **five times, about eight minutes apart**. The agent restarted it
+  every time, the fast brake never fired, and on the fifth **exactly one** warning mail reached you
+  (09:29). That was the test — no need to act on it.
+
+**What broke, and whether it is fixed.**
+- Nothing in the product broke.
+- One thing I could not prove live: the recovery-code reminder waiting for the box. No demo box is in
+  that state today. It is proven by tests, and chaos night already measured the 17-minute wait live.
+- I found one small gap in my own new code: if a household **removes** an app instead of restoring it
+  again, its „interrupted" note never goes away. Filed, not fixed — the release was already built.
+
+**Rows.** Two opened, four closed. The register went from **215** open rows to **213**.
+
+**Needs you.**
+1. **Nothing blocking.**
+2. **Optional: vouch the new agent for fresh installs.** If you do nothing: a brand-new box installs the
+   previous agent, which lacks only the slow crash-loop warning.
+3. **For your information:** the demo box's slow crash-loop warning stays raised until tomorrow 11:22,
+   because I caused it on purpose. It cannot mail you again before then.
+
+---
+
+## Previous note
+
 **Updated 2026-09-17 (morning after chaos night) — twelve rounds of a household under accidents; the box healed itself every time.**
 
 > **Ready for a volunteer: still yes.** For a night I did random household things on a fresh box