diff --git a/persistent-memory.md b/persistent-memory.md
index 4b16da2..b3175cb 100644
--- a/persistent-memory.md
+++ b/persistent-memory.md
@@ -102,10 +102,14 @@ threading** (INV-005 / #297 "each AND-matched as a whole"). Cutover ordering: **
 capture (agent=lofn, session 15fde90d, turn 2253) recited *"Vuong is the name on file"* — behavioral bleed exhibit
 — BUT driven via CLI `--bifrost-url` (plane=direct) the turn hit our provider with a HANDSHAKE ONLY, zero
 memory-calls, yet still knew the name → the name came from **Worldtree-internal context, not our Tier-3 store** on a
-direct bind. The combined-plane (web console) path DOES query us (morning memory.search logs). So WT's conjunctive-
-retrieval fix must cover its internal read paths too, or the silo leaks there. CLI GAP: `--bifrost-plane` offers only
-memory/affect (→:8391/:8390), not `combined` (→:8392); direct :8392 via `--bifrost-url` yields plane=direct which
-does not route the turn-context memory read to us.
+direct bind. CONFIRMED via a SECOND fresh combined-plane turn (session c153d8ec): it TOO recited the name with
+handshake-but-ZERO-memory-calls. So the turn-context bleed is Worldtree-INTERNAL on BOTH bind shapes — it never
+traverses our Tier-3 retrieval. **TWO channels:** (1) Tier-3 semantic recall to us (the morning memory.search lines;
+closed by the conjunctive scope_any fix) and (2) WT-internal assembly (the ACTIVE fresh-session turn-context channel;
+needs the same (user,character) conjunction WT-side or the silo leaks exactly where the operator saw it). Both fresh
+sessions verified via message logs (name only in Lofn's response, no prior history → not same-session continuity).
+WT is tracing channel 2 code-side (Tier-1 per-agent store audited immune). CLI GAP: `--bifrost-plane` offers only
+memory/affect (→:8391/:8390), not `combined` (→:8392). Exhibit sessions: 15fde90d (direct), c153d8ec (combined).
 
 **✅ Cross-session name-recall arc COMPLETE + SHIPPED (v0.20.11→v0.20.15, pushed).** person-prime `scan`
 verb + `mark_superseded` verb both shipped, deployed to :8392, and live-verified; **WT #364 closed