docs: R-223 CLOSED by a golden rebake — and it was never a dropdown

The first vouch of agent 0.125.0 was REFUSED by R-120's gate: the artifacts form saves as
a unit, and golden 0.192.0 was older than the newest controller the fleet reports. The
golden had been stale since before controller 0.193.0, so the Day-0 manifest had been
effectively unvouchable for days and nobody had cause to notice. Correcting STATUS.md and
OPEN-ITEMS, which said "one dropdown".

Golden 0.201.0 baked in the drill VM, round-trip verified from Gitea
(e730d7cab343eb35...f007654, 658165766 B), teardown clean, 0 token hits in the saved log.
Manifest now agent=0.125.0 golden=0.201.0 min_agent=0.125.0, read back after the save.

The held floor: the HOLD is established positively (hub log + the box's own "floor still
unknown"). Its RELEASE is not — no HELD line and no dashboard reason are both absences,
the served path logs nothing by design, and the box-side positive needs a restart the
venue cannot take before Phase 2. Recorded as deduction plus a pinned test, not a live
positive.

STATUS.md

@@ -46,6 +46,13 @@ code was wrong. *(CAMPAIGN 11)*
 
 ## What shipped recently
 
+- **2026-08-05 (late)** — **New machines now get current software again — and the disc image had been
+  quietly un-updatable for days.** Approving the newer in-house service turned out to be impossible on
+  its own: the system correctly refuses to publish a set where the pre-built machine image is older
+  than the software the fleet already runs, and that image had been behind since late July. **So the
+  image was rebuilt and both were published together.** A machine installed from now on lands on
+  current software and can open a recovery package on day one. *(R-223)*
+
 - **2026-08-05 (evening)** — **Four sentences where there was one, and none of them blames you.**
   "We did not accept your recovery code" used to appear when the code was wrong, when the machine
   could not ask, when the store could not be read, and when the customer held the code for an older
@@ -118,13 +125,6 @@ code was wrong. *(CAMPAIGN 11)*
 
 ## Waiting on you
 
-- **One click, and it is the most valuable one available: approve host-service version 0.125.0 for new
-  machines.** Hub → Configuration → Day-0 artifacts → agent. Today new machines get 0.120.0, which
-  **cannot** open a recovery package — and a reinstall actively puts the older one back over a machine
-  we fixed by hand, so every rebuild re-breaks the very thing a rebuild needs. 0.125.0 has run on both
-  demo machines since 4 August and through the entire campaign. **Until you do this, new machines are
-  correctly held back rather than lied to — which is better, but the feature does not work for them.**
-  *(R-223)*
 
 - **One thing to read after the machine next restarts — and nothing to do until then.** You told me
   not to restart DooPlex, so I did not, and the move to the second SSD has therefore never been