memory: reconcile the snapshot to v0.6.1

The snapshot was written at v0.6.0 and the marks-guard fix landed after it.
Updates the in-flight head commit, the test count, and the ahead-of-origin
count so a fresh session is not told a stale number.

persistent-memory.md

@@ -20,8 +20,8 @@ loop it turned out to actually be.
 _As of 2026-09-22:_
 
 - **NOTHING IS IN FLIGHT.** U6 (benches) landed, all four review gates closed,
-  **released as `v0.6.0`** and deployed. Tree clean at `3296a86`, 607 tests
-  green, 19/19 booths 200 live. ⚠ **NOT PUSHED** — push is the operator's call
+  **released as `v0.6.0`**, with the last open defect closed in `v0.6.1`. Deployed;
+  tree clean at `1b394dd`, 611 tests green, 19/19 booths 200 live. ⚠ **NOT PUSHED** — push is the operator's call
   and he did not give it this session; `main` is ahead of `origin/main`.
   → `persistent-memory.d/2026-09-22-u6-benches-released.md`
 - **v1 is gated on seven units. SIX ARE LANDED. U7 IS THE LAST ONE.** U1
@@ -61,8 +61,8 @@ _As of 2026-09-22:_
 - **A remote exists and `main` is AHEAD of it.** `origin` is
   `git@gitea.phasefinal.com:vh/booth.git`; the first push of this repo's history
   was 2026-09-22 (26 commits, `v0.2.0`–`v0.5.0` in one motion). As of this
-  snapshot `main` is **8 commits ahead of `origin/main`** — the whole of U6
-  including `v0.6.0`. Pushing is the operator's call.
+  snapshot `main` is **11 commits ahead of `origin/main`** — the whole of U6
+  including the `v0.6.0` and `v0.6.1` tags. Pushing is the operator's call.
 - **Two dated predictions are pending and must not be run early.** U5's adoption
   re-measure on **2026-09-29**; the `.forever` re-count **on or after
   2026-10-06**. Before the second, read