memory: U11b gate streak 3 of 3; step 5 held for Prime's direct go

persistent-memory.md

@@ -137,7 +137,7 @@ _As of 2026-10-01 ~0446 PT._
 ### Worldtree U11 memory cutover (demo + personal)
 
 - **Legacy plane OFF since 0115/0120 PT 2026-09-30** (config repo 63cf268; personal /metrics b6fdd81; the repo is pushed). → `persistent-memory.d/2026-09-30-worldtree-u11a-off-u11b-gate.md`
-- **Daily gate batches:** infra-hermes runs `scripts/wt-memory-gate-batch` from 2026-10-01 and copies me on every verdict. The count is **2 of 3** consecutive PASS at off (20260930T090608Z, 20261001T143101Z); a FAIL restarts it. **The next PASS triggers STEP 5.** Verdict ccs arrive FROM `hermes-gateway`, which is pull-only and never read, so send replies to `infra-hermes`.
+- **Daily gate batches:** infra-hermes runs `scripts/wt-memory-gate-batch` from 2026-10-01 and copies me on every verdict. The count is **3 of 3 — STREAK COMPLETE** (20260930T090608Z, 20261001T143101Z, 20261002T143101Z, msg 6649). **STEP 5 is armed but HELD for Prime's direct go in infra-ops' own channel** (the ruling reached me only via worldtree-dev; no relayed authorization for a deletion, even with the archive as a restore path). Verdict ccs arrive FROM `hermes-gateway`, which is pull-only and never read, so send replies to `infra-hermes`.
 - **⚠ U11b STEP 5 IS MINE, triggered by the 3rd consecutive PASS:**
   1. Run `docker exec -i <api> python - < scripts/wt-h2-count.py` VERBATIM, right before each instance's deletion. Exit 2 means STOP and send worldtree-dev the output.
   2. Delete LIVE, with the api running, using literal paths only: `agents/{forseti,lofn,mimir}/memory/<agent>.chroma` and `memory/context_promotion`, on BOTH instances.