R-840/R-859/R-860 records: 11 §5.3.1 + §5.4.2, 03, 04, 00; runbooks config-bundle + os-updates-test-waits; register 333→334 (R-840/859/860 closed, R-861/862 opened); STATUS; report; evidence

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

STATUS.md

@@ -1,10 +1,44 @@
 # STATUS — what works, what's broken, what's next
 
-**Ready for the first real tester (Tester-2): yes. You confirmed the tunnel route and the connect mails (2026-09-30).**
+**Ready for the first real tester (Tester-2): yes. Tester 2 is installed and running (since 2026-10-04 18:06).**
 
-**Updated 2026-10-04 (late evening): the hub has a System page with every box's versions and the update buttons; Docker
-updates are built; a crashed box restarts by itself, at most twice an hour. Both demo boxes run host agent 0.142.1 and
-controller 0.292.0. Hub 0.132.0. Installer 1.30.0. New installs get golden 0.292.0 (re-made: live-restore on, Docker 29.8.2) with agent 0.142.1.**
+**Updated 2026-10-04 (night): installed boxes can now get new root files by a signed job; test approvals end with the
+test; the controller repairs itself after a Docker socket restart. Both demo boxes run host agent 0.143.0 and controller
+0.293.0. Hub 0.133.0. Installer 1.31.0. New installs get golden 0.293.0 with agent 0.143.0.**
+
+## Today (2026-10-04, night): root files for installed boxes, test approvals, Docker self-repair
+
+**Decisions I took myself (you may reverse each):**
+- The hub cancelled only the AUTOMATIC test approvals of today (guest and host fixes). Your own "Approve Docker set"
+  press stays in force. From now on every approval made during a test wait gets the test mark, button or not.
+- A box whose root files are behind the approved ones for 7 days sends you a mail.
+- The demo boxes' controller floor is 0.293.0; the fleet floor stays 0.292.0, so Tester 2's controller did not move.
+
+**What I did:**
+- **Root files for installed boxes (your ruling):** a box's root-owned files (permissions list, helper scripts, crash
+  guard) now travel as one signed package. The box checks your signature, every file and itself; on any problem it
+  puts the old files back. Proven on both demo boxes: a wrong package refused, a package with one changed line
+  installed and undone, a copied old job refused. New installs use the same package.
+- **One catch:** a box installed before tonight cannot take the FIRST package by itself; it needs one small step by
+  hand. I did it on both demo boxes. **Tester 2 needs it from you** (below).
+- **Tester 2 was not as old as the brief thought:** it was installed at 18:06 local, after the crash guard and the new
+  image. It already has the crash guard, live-restore and Docker 29.8.2. It lacks only tonight's Docker-update fix. I
+  sent it the signed agent update.
+- **Test approvals end with the test:** the hub cancelled today's 4 test approvals at its restart (you got one mail).
+  Tester 2 keeps what it installed; no further box installs them. The same fixes get a real approval after 24 h + a night.
+- **Docker self-repair:** if Docker's socket is re-created, the controller now restarts itself and the web router within
+  about 2 minutes. Proven on the scratch box and on demo-hp, no app restarted.
+- **drill-r50 is gone** from the hub. On ep0 nothing was destroyed (it had no backups there); its tunnel entry left.
+- The "felhom-pbs skipped" line on Tester 2 is normal for a new box's first hour (no mail was sent).
+- New-install image 0.293.0 baked and approved.
+
+**Needs you (nothing breaks if you wait):**
+- **Tester 2's one-time step** (5 minutes): connect your tunnel, `ssh -p 8822 felhom-op@10.77.0.5`, reveal the root
+  password in the hub (Hosts → Tester-2 → Console access; this writes one line on Tester 2's timeline), `su -`, then
+  run the three commands in `documentation/runbooks/config-bundle.md` ("Tester 2"). Tell me when done; I send the package.
+  If you wait: Tester 2 keeps working; it just cannot get new root files until then.
+- **Found, not fixed:** the agent's permission list is wider than "minimal": a broken-into agent could become root on
+  its own box. Worth fixing before the first paying customer.
 
 ## Today (2026-10-04, ~18:30): you found a bug — the Docker update blinded the box's controller