correct the vouch state: the operator vouched 0.208.0 DURING this session

Recorded on arrival as 0.207.0, re-read from live hub_settings at the end and it is 0.208.0 — the
operator acted while the session ran. The ask is therefore 0.208.0 -> 0.209.0, not 0.207.0 ->
0.209.0, and STATUS.md plus the golden evidence now say so.

Caught only because the state was re-read rather than carried forward from the arrival note. A fact
recorded at the start of a long session is a fact about the start of the session.

STATUS.md

@@ -69,11 +69,10 @@ per-guest network health, which we already lost 1 h 15 m to once.
 
 ## Waiting on you
 
-- **One approval, and now it is the only one: the new base image.** Baked, published, byte-checked —
-  and **installations receive an older version until you press Save.** Hub → Configuration → Day-0
+- **One approval: move the base image on by one.** You vouched **0.208.0** during the night —
+  thank you, that gap is closed. Today's release went one further, so: Hub → Configuration → Day-0
   artifacts → Golden **0.209.0** → Save. One field moves, the other two were checked and are right,
-  and it is reversible. It supersedes last night's unvouched 0.208.0, so this is one decision, not
-  two. *(R-242)*
+  and it is reversible. *(R-242)*
 - **Fourth time in three days, so worth a minute.** A check now catches the *baking* being forgotten
   — it caught it again today and refused the push until it was done. **Nothing catches the approval
   being forgotten.** Two ways to close that are written up, neither built. *(ROADMAP G-8)*