memory: snapshot — FULL COVERAGE proven (verbose persona too): sindra-probe theatrical turn promoted the user fact cleanly under Stage 2/v0.36.0 + cold-recalled @0.694; :8081 confirmed on v0.36.0; closes the verbose-persona caveat end-to-end. Operator session: :8391 wiped, ratatoskr-web up :8765 (consumer key, sindra in picker) — persona+debug only, web client does NOT bind :8391 (#17 unbuilt = no memory persistence in web chat)

persistent-memory.md

@@ -60,11 +60,19 @@ The whole #296 arc closed this session:
   the verbose drop; hard-linguistic layer at #305. Live-validated eval fixture pair handed to worldtree-dev
   (terse-proof POSITIVE chunk + choc-v2/sindra NEGATIVE).
 
-**OPEN / OPTIONAL** (operator greenlight, no rush): verbose-sindra re-smoke vs demo v0.36.0 with a FRESH
-agent + end_user (dodge the dedup) = the full-coverage proof (verbose characters remember too). Needs demo
-setup for our provider OR v0.36.0 reaching personal `:8081` (still v0.35.19). worldtree-dev thread CLOSED;
-althing monitor armed. Shipped this session (all on `main`, NOT pushed): v0.17.6 (`96d61a4`) + spec repin
-v0.35.16 (`4eee7c8`) + snapshots.
+**FULL COVERAGE PROVEN (the OPEN item, now DONE):** re-smoked the VERBOSE persona — `ratatoskr:sindra-probe`
+(sindra's actual theatrical prompt, end_user `verbose-v2`, FRESH agent to dodge the WT promotion-dedup) against
+`:8081` **v0.36.0**: the high-volume theatrical turn promoted the USER FACT cleanly (not a meta-description) and a
+COLD history-free session recalled it @ 0.694 — "Dark chocolate. With sea salt." So `:8081` is on v0.36.0 and
+verbose characters remember too. All session commits + tags PUSHED to origin (v0.17.6, spec repin v0.35.16,
+snapshots; tags v0.17.4/.5/.6).
+
+**NOW (operator session):** `:8391` store WIPED clean; `ratatoskr-web` UP on `0.0.0.0:8765` (LAN
+`http://10.100.10.50:8765`) — consumer key (owner-matches sindra) + end_user `vuong`, `ratatoskr:sindra` added to
+the local picker; operator is spending time with Sindra via the web UI. **CAVEAT: the web client does NOT bind to
+our `:8391` provider (#17 unbuilt) → the web chat is the PERSONA + debug-surface experience; Sindra does NOT
+persist/recall memory there** (the proofs above used manual bound sessions via scripts, not the client). worldtree-dev
+thread closed; althing monitor armed.
 
 **(2026-06-16 PM) — BIFROST REPINNED 0.7.0→0.8.0 (wire v0.5→v0.6).** The
 memory `search` scope filter was split into `scope_all` (AND/intersection) +
@@ -245,6 +253,8 @@ decision. Captures rationale that won't be obvious from code alone.
 - `[2026-06-18]` **#296 Stage 2 (v0.36.0) MERGED at worldtree-codex** — user-only one-call-per-turn extraction, the STRUCTURAL fix for the subject-inversion drop sindra exposed. Staged per operator: core fix now (validated by our terse-probe PASS + WT test suite); hard-linguistic layer (larger-model escalation, marker-less-fact regex-demotion) tracked at Worldtree #305. We handed worldtree-dev a live-validated eval fixture PAIR for #305 (terse-proof POSITIVE chunk + choc-v2/sindra NEGATIVE-drop).
 - `[2026-06-18]` **Full root-cause chain traced + confirmed** (a3466fab ledger pull via infra-ops): v0.35.16 verbose-sindra EMITS 2 meta-descriptions → v0.35.19 gate hard-rejects them (emit-then-reject) → v0.36.0 user-only pass emits the fact. The 2 v0.35.16 chunks ("Assistant's detailed flirtatious response…" / "…head tilt, eye locking, freckles…") are textbook subject-inversion; banked as #305 negative-fixture examples.
 
+- `[2026-06-18]` **FULL-COVERAGE proof — verbose-persona memory works under Stage 2 (v0.36.0).** Re-smoked `ratatoskr:sindra-probe` (sindra's theatrical prompt; FRESH agent + end_user `verbose-v2` to dodge the WT promotion-dedup): the high-volume turn promoted the user fact CLEANLY (not a meta-description) and cold-recalled @ 0.694. Confirms `:8081` is on v0.36.0 and closes the verbose-persona caveat end-to-end. Then started `ratatoskr-web` (`:8765`, consumer key, `ratatoskr:sindra` in the picker) for the operator's Sindra session — **persona + debug only; the web client does NOT bind to `:8391` (#17 unbuilt), so no memory persistence in the web chat** (memory-enabled chat is the #17 build, or a manual bound session).
+
 _For per-issue TDD implementation notes, Volva findings, and contract amendments, see the git log — every per-issue commit carries a structured message capturing the trail._
 
 ## Tried and abandoned