golden 0.216.0: baked, published, vouched — gates green again

Closes the two-release day-0 gap that has been convicting CI since
2026-08-14. Run against RUNBOOK-manual-build.md 4.0 + 4.1.

  GOLDEN_VERSION = 0.216.0
  GOLDEN_SHA256  = ac004dc90d8cefccc5448377892f9cff3a4c3e1e27d0e11129120e38ac31c34b
  archive        = 656,970,239 bytes, controller image 0.216.0
  template       = debian-13-standard_13.6-1_amd64.tar.zst (listed live, not reused)

Baselines re-read on the machine and all four matched the sheet: controller
v0.216.0, its MinAgent 0.129.0, agent v0.129.0, previous golden 0.214.0. The
published agent artifact for the vouched agent_version was confirmed present
in the package registry rather than inferred from a CHANGELOG, and the R-216
check passed on the machine: MinAgent is EQUAL to, not above, the newest
published agent.

Verified beyond the script's own claim: the artifact was downloaded back out
of Gitea and hashed, and it matches GOLDEN_SHA256 exactly. A script printing
a digest and the registry serving those bytes are two different claims.

Pass markers (corrected post-R-233 list) all present, quoted with line
numbers in pass-markers.txt; excluding/FATAL absent; there is no mp1.

Token never reached a command line: copied file->file, read inside the VM by
the runner. systemctl show grep = 0. Token-leak grep on the COMMITTED log run
with its positive control FIRST -- seeded copy 1, real log 0 -- because a
grep -c that matches nothing also returns 0.

Teardown: guest destroyed and purged, token/runner/script/log shredded AFTER
the log was copied out, qemu exit confirmed with ps -eo comm (not pgrep -f),
disk reverted to virgin.

Vouched by the operator; verified by reading the hub's own store: golden
0.216.0 / agent 0.129.0 / min_agent 0.129.0, and the hub's recorded sha256
matches the independently downloaded artifact. That check was necessary
because golden_currency_gate.py says of itself that it checks the BAKE, not
the vouch.

repo_gates.py --fast now rc=0, all nine gates OK -- first fully green run
since 2026-08-14.

Capability map deliberately NOT changed: the day-0 row cites drill documents,
and the map's only golden literal is a dated historical citation on the
recovery-journey row which bumping would falsify.

R-334 is closed in a follow-up commit quoting this push's CI run id, since
closing it without one would leave the ambiguity a third time.

STATUS.md

@@ -1,7 +1,7 @@
 # STATUS — what works, what's broken, what's next
 
-**Updated 2026-08-18 (midday — a listening socket that served nobody, then a rehearsal upgrade that changed nothing; off-site backups were down for
-9½ hours overnight and are back).**
+**Updated 2026-08-18 (afternoon — a listening socket that served nobody, a rehearsal upgrade that changed
+nothing, and a new install that is finally current).**
 
 > **A view, not a source.** `documentation/backlog/OPEN-ITEMS.md` is the authority; this page restates
 > part of it in plain words, and **nothing may exist only here**. **Items, not paragraphs. One screen.**
@@ -43,6 +43,13 @@ record with no machine** — created 13 August, no host, no backups, nothing to
 
 ## Shipped
 
+- **A new machine installed today finally gets today's software** (R-334, closed). The pre-built image
+  had been two releases behind since the 14th — anyone installing would have received a version
+  missing last week's disk-warning fix *and* the follow-up that corrected it. A fresh image was baked
+  and published, and **you vouched it**, which was the half that could not be done without you. **The
+  build system is green again for the first time since 14 August**, so the failure mail should stop.
+  The running machines were not touched: this only ever affected *new* installs.
+
 - **Last night's two backup alarms were real, and are fixed** (R-336). Both machines failed their
   off-site backup at 04:30; **neither machine was at fault**. The off-site box in Germany had run out
   of one internal resource and, while looking perfectly healthy from outside, was accepting no