memory: /snapshot — silo test is the immediate post-clear action

Current state now leads with the (user,character) memory silo test:
store born-fresh, throwaway betty ready, Sindra off-limits, waiting on
WT #368 fix deploy. tier3 CLI fixed (v0.21.1). Handoff written for the
post-clear session.

persistent-memory.md

@@ -1,6 +1,6 @@
 # Persistent memory — ratatoskr
 
-_Last updated: 2026-07-17_
+_Last updated: 2026-07-18_
 
 > **Always check for `/tmp/ratatoskr-dev-handoff.md`** — if it exists and its
 > `Written:` stamp is under an hour old, read it (it carries the in-flight
@@ -44,9 +44,22 @@ upstream API key stays server-side (INV-003).
 
 ## Current state / in-flight
 
-_As of 2026-07-17:_
+_As of 2026-07-18:_
 
-**▶️ NEXT: FORK ratatoskr for arbo image-gen (operator call 2026-07-17).** The arbo debug-observability
+**▶️ IMMEDIATE (the reason for this clear): RUN THE (user, character) MEMORY SILO TEST.** WT #368's fix
+(conjunctive `{end_user, agent_self}` write + read) is being deployed by worldtree-dev ("dev team done coding";
+personal `:8081` / b125). When live, run the Alice/Betty silo demo on ratatoskr's live surface. **FULL SETUP +
+PROTOCOL is in the #368 note below** ("LIVE SILO TEST IN PROGRESS"). Quick version: store is born-fresh (0 chunks);
+throwaway **`ratatoskr:betty`** created (delete after with `uv run python -m ratatoskr.tier3 delete ratatoskr:betty`
+— the tier3 CLI is now FIXED for b125, v0.21.1); **⚠️ SINDRA IS OFF-LIMITS — delete ONLY betty.** Test: Sindra says
+"coffee > tea", Betty says "tea > coffee" (drive via web `:8765`, `bifrost_plane:"combined"`, ~6 turns each to trip
+the idle-scan promotion) → verify each promoted chunk's scope is `{end_user, agent_self}` AND each agent's
+conjunctive read returns ONLY its own preference (Sindra must NOT recite Betty's tea; vice-versa). Pre-fix it
+leaks (OR-union); post-fix it silos. Detecting the fix is live: a promoted chunk carries `agent_self` in scope (vs
+`{end_user}`-only pre-fix), or a worldtree-dev/infra-ops deploy ping (monitor armed). Follow-ups after: the rev-1.2
+enforcement read is DONE (3 findings folded → rev 1.3); the backfill live-verify (synthetic legacy corpus) is queued.
+
+**▶️ NEXT MAJOR: FORK ratatoskr for arbo image-gen (operator call 2026-07-17).** The arbo debug-observability
 idea did NOT become a feature bolted onto ratatoskr. Operator decision: **ratatoskr stays the Worldtree
 debug surface; the arbo image-gen product becomes a FORK of ratatoskr** (clean chat-first surface, debug
 panes hidden by default). The fork is the next major workstream; "get ready to assist with fork" is the