REPORT: the golden debt named in section 12 was paid the same day

Golden 0.226.1 baked, published, round-trip verified, vouched, floor raised.
golden_currency_gate.py red -> green on the same command, so the three declared
--no-verify bypasses are historical rather than standing.

The fleet state changed with it: both demo machines run 0.226.1, and
demo-felhom got there by SELF-UPDATE rather than by hand -- which is the
positive observable that the floor is acting and not merely set.

REPORT.md

@@ -122,7 +122,16 @@ tell which it has — so the fix shipped as **0.226.1** and the box was redeploy
 therefore describes 0.226.0**, and that is stated rather than quietly re-attributed; 0.226.1 differs
 from it only by `CountsUnknown` and its two tests, neither of which touches any path §6 exercised.
 
-**`demo-hp` only.** `demo-felhom` stays on 0.225.0 and the rest of the fleet on 0.223.0 (the floor).
+**Fleet state at the end of the session — the debt named in §12 was PAID the same day.** Golden
+**0.226.1** was baked, published, round-trip verified, **vouched** and the floor **raised to 0.226.1**.
+Both demo machines now run 0.226.1, and `demo-felhom` got there by **self-update**, not by hand:
+
+```
+[selfupdate] Post-update startup: update successful (0.225.0 → 0.226.1)
+```
+
+`golden_currency_gate.py` went **red → green** on the same command. Evidence:
+`felhom.eu/documentation/tests/golden-0.226.1-2026-08-30/`.
 
 ## 6. Live validation — endpoint level, on `demo-hp`
 
@@ -292,13 +301,17 @@ destructive restore.
 
 ## 12. Two gates fired; one push was bypassed, and both are declared
 
-**`felhom.eu` — `golden-currency` CONVICTED.** Three controller releases shipped today (0.224.0,
+**`felhom.eu` — `golden-currency` CONVICTED, and the debt is now PAID.** Three controller releases
-0.225.0, 0.226.0) and the vouched golden still carries **0.223.0**, so a machine installed right now
+shipped today and the vouched golden still carried **0.223.0**, so a machine installed at that moment
-receives none of them. **The gate is right.** A **BYPASS, not a waiver**, on the operator's standing
+would have received none of them. **The gate was right.** Those pushes used `git push --no-verify` — a
-ruling from earlier today — re-checked for this release rather than reused blindly: all three are
+**BYPASS, not a waiver**, on the operator's standing ruling, re-checked for this release rather than
-invisible to a day-0 box, and a *restore-surface* fix in particular has nothing to act on there.
+reused blindly.
-**The ground expires the moment a release changes first-boot behaviour.** Tracked on **R-242**; **one
+
-bake carrying 0.226.0 covers all three**, then raise the floor to 0.226.0.
+**Later the same day the operator asked for the bake, and it was done: golden 0.226.1 baked, published,
+round-trip verified, vouched, and the floor raised.** The gate went **red → green**, so those bypasses
+are **historical rather than standing**. See §5 for the fleet state and
+`felhom.eu/documentation/tests/golden-0.226.1-2026-08-30/` for the evidence, including the round trip
+and the proven token-leak grep.
 
 **`felhom-controller` — nothing was bypassed.** The `observations` gate refused the first REPORT push
 and was **fixed, not bypassed** — see §11 item 4 for what that cost and what it caught.