golden 0.246.0 baked and vouched with agent 0.132.0; controller floor 0.246.0 (operator decisions)

Decision 1 delivered: floor 0.246.0 served, the N100 on 0.246.0 within seconds;
Peti's box is DOWN on the hub and receives it when it reports.

Decision 2: the agent vouch was refused by R-120 until a newer golden existed.
On the operator's choice, golden 0.246.0 was baked (sha 05b7559d, amd64, all
markers, token leak 0 with control 1, registry 200 before teardown) and vouched
together with agent 0.132.0. golden_currency_gate: WAIVED -> OK. Bake evidence
filed where the gate and runbook read it: tests/golden-0.246.0-2026-09-17/.

Recorded, none reaching the registry: a first attempt on the arm64 template
(my version sort), a self-matching pkill, and an OOM-killed watcher whose
post-bake steps were done by hand.

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

REPORT-chaos-fixes-2026-09-17.md

@@ -78,3 +78,29 @@ made unattended — the operator's to take, and cheap to take.
 1. An interrupted-restore notice for a removed app never clears. **FILED: R-552**
 2. No Tier-0 box can exercise the paused + agent-connected escrow state. **FILED: R-551**
 3. Controller `handler.go` and agent `controllersupervisor_test.go` were not `gofmt`-clean before this task. **NOT-A-FINDING: pre-existing formatting only; reformatting unrelated lines was left out to keep the diffs reviewable.**
+
+## Addendum — the operator's two „yes" answers, carried out (2026-09-17, afternoon)
+
+**1. Controller floor raised to 0.246.0** (declared MinAgent 0.131.0). Hub: `Global controller-version floor
+set to "0.246.0"` and `managed floor SERVED for demo-felhom … from declared`; the N100 ran 0.246.0 within
+seconds (`at/above floor 0.246.0 (we are 0.246.0)`). demo-hp runs 0.246.0 (it has a per-customer override at
+0.243.0). **Peti's box is DOWN on the hub** (last controller 0.115.0) and receives it when it reports.
+Evidence: `audits/evidence-chaos-fixes-2026-09-17/decision1-floor-0246.txt`. The „recommendation not followed"
+above is therefore superseded by the operator's decision.
+
+**2. Agent 0.132.0 vouched — which required a golden.** The first vouch was refused by the hub's R-120 gate
+(`golden 0.245.0 is older than the newest controller the fleet reports (0.246.0)`); nothing was stored. Asked,
+the operator chose to bake. **Golden 0.246.0** baked by RUNBOOK-manual-build §4.1, sha `05b7559d…`, amd64,
+all markers, token leak 0 (control 1), registry 200 before teardown; then vouched together with agent 0.132.0:
+`Artifact manifest set: agent=0.132.0 golden=0.246.0 min_agent="0.131.0" wrapper_sha=true`, read back
+exactly. `golden_currency_gate.py` moved from WAIVED to **OK**. Evidence: `tests/golden-0.246.0-2026-09-17/`.
+
+**Mistakes of mine on the way, none reaching the registry:** the first bake attempt used the **arm64**
+template (my version sort), aborted before anything was built; stopping it, a self-matching `pkill` killed my
+own shell; the second attempt's watcher was killed for low memory and its post-bake steps were done by hand.
+
+**Observation.** 4. `golden_currency_gate.py` reported the newest bake as 0.242.0 although 0.243.0–0.245.0
+were baked and published, because those bakes filed their logs under `audits/` rather than
+`documentation/tests/golden-<ver>-<date>/`. **NOT-A-FINDING: a recording slip in earlier bakes (including
+0.245.0, mine), not a gate defect — the gate reads the place the runbook names; 0.246.0 is filed there and the
+gate reads it.**