memory: U11a overnight log sweep clean but traffic-free; re-sweep TODO

persistent-memory.md

@@ -125,7 +125,7 @@ _As of 2026-09-30 ~0120 PT._
   - ⚠ **`off` MUST be quoted.** `core/defaults.py` uses `yaml.safe_load`, which is YAML 1.1: a bare `off` parses as boolean False and the strict `LegacyMode` enum refuses the boot. Verified at 64f79b38 with Worldtree's own `load_cutover_config`. worldtree-dev's recipe had it bare.
   - **DEMO flipped at 0115 PT** with `deploy-wt-config deploy demo`. The gauge reads `worldtree_memory_legacy_mode{kind="off"} 1.0`, /health is 200, and the boot log is clean. The staged read_only file is deleted. Rollback: set legacy.mode to `"live"` in the repo and deploy it.
   - **PERSONAL flipped at 0120 PT** on 64f79b38a7fb, the same way. ⚠ Personal has **no /metrics**, because the #308 metrics block is demo-only, so the proof was the no-metrics one: an in-container `get_default→load_cutover_config→validate_cutover` gave off/writer/reader True, /health was 200, and the boot log matched the pre-flip one. Whether to add metrics to personal is still worldtree-dev's open call. Both instances are in sync with the repo.
-  - Watch after each flip: any `legacy executor <kind> invoked with memory.legacy.mode=off; ignored` line goes to worldtree-dev with its stamp.
+  - Watch after each flip: any `legacy executor <kind> invoked with memory.legacy.mode=off; ignored` line goes to worldtree-dev with its stamp. A sweep at 0154 of both logs since their last start found **0 watched lines, but there was ~no traffic** (demo 0 real requests, personal 1), so that proves little. **TODO: re-sweep after the first real traffic** with `docker logs --since <StartedAt>`, grepping `legacy executor|Traceback|ERROR|will not be remembered`. A CI recreate drops the old container's log.
 - **U8 window batches (infra-hermes, Prime's 2340 ruling): likely VOID now that the read_only window is skipped.** The wrapper is NOT built; I asked worldtree-dev whether the plan is dead or has a replacement (e.g. `--legacy-mode off`). If it revives, the harness facts are in thread `01M3RG8RDFSFGDK6BDFTE6ZCJE`, in `persistent-memory.d/2026-09-29-worldtree-u11a-prepped.md`, and as follows. Run it from nh3-dev `~/development/Worldtree`, which is worldtree-dev's tree: NEVER check out or reset it. Each batch takes about 10-15 min, runs under a flock, and must not git-commit; a FAIL goes to worldtree-dev the same day and is never retried.
 
 ### nh3-pve + nh3-ml1: post-visit, all live (2026-09-25/26)