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

2026-10-02 07:50:12 -07:00
parent 59fb6b77a8
commit 6e15f610bc
2 changed files with 2 additions and 2 deletions
@@ -14,7 +14,7 @@
 **The U11b gate (Prime 0320 via worldtree-dev, thread `01M3SGEQDRQD7DWBVT4K73FAHP`):**
 - DELETE the live legacy data on both instances after **3 consecutive PASS batches at off**. A FAIL restarts the count.
 - infra-hermes runs the daily batch, `scripts/wt-memory-gate-batch`, in a detached worktree at demo's deployed sha. Its exit codes are 0 PASS / 1 FAIL / 2 error / 3 refused / 4 busy.
- Count: **2 of 3** — 20260930T090608Z PASS (user median 0.83); 20261001T143101Z PASS (first daily batch, infra-hermes, cc msg 6179). The 0930 run started by accident from a test meant to be `--dry-run`. worldtree-dev's controls 080927Z and 082829Z each FAILed by one flip and were the instrument check, not the streak.
+- Count: **3 of 3, complete** — 20260930T090608Z PASS (user median 0.83); 20261001T143101Z PASS (first daily batch, infra-hermes, cc msg 6179); 20261002T143101Z PASS (user median 0.83 over runs [0.92, 0.83, 0.83], msg 6649). Step 5 held 2026-10-02 0750 for Prime's direct go (the ruling was relayed). The 0930 run started by accident from a test meant to be `--dry-run`. worldtree-dev's controls 080927Z and 082829Z each FAILed by one flip and were the instrument check, not the streak.
 - Step 5 is mine:
  1. Run `scripts/wt-h2-count.py` VERBATIM inside each api container. The rehearsal on copies read 0 on both instances.
  2. Delete LIVE, with the api running, using literal paths.