docs: REPORT.md — delivery is DONE (golden 0.229.0 vouched, floor raised)

Section 6 now records the completed delivery instead of an owed bake; observation 2 records that
R-242's sixth conviction was paid the same day and the declared --no-verify bypass is historical.
New section 15 carries the bake, the round trip, the third independent reader, both proven
pre-gates, the three-field vouch, the R-120 gate passing, and the floor proven ACTING.

REPORT.md

@@ -56,7 +56,9 @@ Re-checked before the first edit, and both matched the task's table exactly. **N
 | `felhom-controller` | `4c8f0d291948fd60887c0fd7066e63df9e3abb68` | R-103 — Part 2.2 + Groups C and D |
 | `felhom-controller` | `8aa95b58319f947fa9b3de38cb410b9d2756332f` | CHANGELOG / CONTEXT / README / REUSE / REPORT |
 | `felhom.eu` | `c2de785bf27631284fa5ab525e0f32494804773a` | architecture, register, STATUS, drill evidence — pushed with `--no-verify`, declared |
-| `felhom-controller` | *(this §3 fill-in)* | commit hashes recorded after the fact |
+| `felhom-controller` | `0957f43d108e4166c545e4fbb5e11481594ec218` | commit hashes recorded in §3 |
+| `felhom.eu` | `83ff9e8e3856fa822bfa1f80fc305783964aef68` | golden 0.229.0 bake record, R-242 paid, STATUS — pushed with the hook ARMED, no bypass |
+| `felhom-controller` | *(this update)* | §6 and §12.2 rewritten for the completed delivery |
 
 ## 4. Per-test results, and the five named red-proofs
 
@@ -97,9 +99,15 @@ gitea.dooplex.hu/admin/felhom-controller:0.229.0 Up 22 seconds (healthy)
 Built locally (`build.sh 0.229.0 --push`) from a clean, pushed tree; deployed to demo-hp guest 9201 by
 the bootstrap mechanism (`docker pull` → `/etc/felhom-controller-image` → restart the unit).
 
-**Fleet delivery is NOT done and is the operator's (R-242).** The fleet floor and the vouched golden
-are **0.228.0**; **a golden carrying 0.229.0 is owed**, then the floor raised. `golden_currency_gate.py`
-convicts correctly and the `felhom.eu` push used `git push --no-verify` — see §13, Observation 2.
+**Fleet delivery is DONE** — on the operator's explicit instruction, given after the report above was
+first written. Golden **0.229.0** baked, published, **round-trip verified** (656 864 331 B, sha256
+`39aa886d…d7bdae87`, both identical to what the bake reported; `./etc/felhom-controller-image` read out
+of the *downloaded* archive says `felhom-controller:0.229.0`), **vouched** as a three-field change
+(`golden_version` 0.229.0 · `agent_version` 0.130.0 · `min_agent` 0.129.0, the last read from this
+CHANGELOG's header rather than assumed), and the **fleet floor raised to 0.229.0**. Verified by
+re-reading the manifest, not by trusting the flash. **The floor is proven ACTING:** `demo-felhom`
+self-updated `0.228.0 → 0.229.0` with nobody deploying to it. `golden_currency_gate.py` went red →
+green. Evidence: `felhom.eu/documentation/tests/golden-0.229.0-2026-08-31/`.
 
 ## 7. NOT yet live-validated — per matrix row, deliberately
 
@@ -230,13 +238,14 @@ re-runs it. **No catalogue file was changed.**
    one. That is a reading of the code, not a test. Filed with the exact experiment that would settle it.
    Not fixed here: §12 of the task forbids expanding scope, and this is a capture-path change.
 
-2. **FILED: R-242 — the golden-currency gate convicted for the sixth time, and the
-   `felhom.eu` push used `git push --no-verify`.** v0.229.0 is released and the newest golden carries
-   0.228.0, so a machine installed now receives neither fix. **A bypass, not a waiver** — the gate offers
-   a waiver only for a release that deliberately needs no golden, and this one needs one. **The day-0
-   ground was re-checked, not reused:** R-102/R-103 are restore-surface changes on the Tier-2 card and a
-   day-0 box has taken no Tier-2 copy; no first-boot behaviour changed; `MinAgent` unchanged at 0.129.0.
-   **Owed: bake a golden carrying 0.229.0, vouch it, raise the floor.**
+2. **FILED: R-242 — the golden-currency gate convicted for the sixth time; the debt was then PAID the
+   same day.** The first `felhom.eu` push used `git push --no-verify` (a **bypass, not a waiver** — the
+   gate offers a waiver only for a release that deliberately needs no golden, and this one needed one),
+   with the day-0 ground re-checked rather than reused. **The operator then instructed the bake, and it
+   was done:** golden 0.229.0 baked, published, round-trip verified, vouched and the floor raised; the
+   gate went **red → green** and the declared bypass is now historical. **The half of R-242 that stays
+   open is untouched: nothing gates the VOUCH itself**, so a baked-but-unvouched golden still passes the
+   currency gate silently. Cadence, measured not asserted: **two bakes in one day** (0.228.0, 0.229.0).
 
 3. **NOT-A-FINDING: it is my own process error, and its durable home is the MEMORY, not the product
    register — which is where the first two instances already live and where I have added this one
@@ -289,5 +298,25 @@ re-runs it. **No catalogue file was changed.**
 ```
 felhom-controller/controller$ go build ./... && go vet ./... && go test ./...   → all ok
 felhom-controller$ python3 controller/scripts/controller_gates.py               → all 13 gates OK
-felhom.eu$ python3 scripts/repo_gates.py       → 11 OK, golden-currency FAILED (declared, §12.2)
+felhom.eu$ python3 scripts/repo_gates.py                                         → all 12 gates OK
 ```
+
+## 15. Delivery — the bake and the vouch (added after the operator instructed it)
+
+| | |
+|---|---|
+| `GOLDEN_VERSION` | **0.229.0** |
+| `GOLDEN_SHA256` | `39aa886df77b21757aef3b298a389343dc0df5134bb0f14e8f92a451d7bdae87` |
+| size | **656 864 331 B** |
+| round trip | downloaded bytes match the bake on **both** size and sha |
+| delivered artifact | `./etc/felhom-controller-image` read out of the DOWNLOADED archive → `felhom-controller:0.229.0` |
+| third reader | the hub's own Day-0 dropdown read the same sha from Gitea, before anything was vouched |
+| acceptance markers | 1/1/1/1 present, 0/0/0 absent, counted on the committed log |
+| 404 pre-gate | proven with a positive control (0.228.0 → 200) before the 404 was believed |
+| token leak grep | proven with a positive control (a seeded copy grepped 1) before the 0 was believed |
+| vouch | three fields, verified by **re-reading the manifest** — not the flash |
+| R-120 gate | **passed**, not bypassed (fleet newest 0.229.0, golden 0.229.0) |
+| floor | raised to 0.229.0; **proven ACTING** — `demo-felhom` self-updated `0.228.0 → 0.229.0` unattended |
+| teardown | build guest 9100 `--purge`'d, token/script/log shredded **after** the log was copied out, VM powered off, disk reverted to `virgin` |
+
+Full record: `felhom.eu/documentation/tests/golden-0.229.0-2026-08-31/`.