vh
ff1f9ca1e8
- #368 (user,character) memory silo test DONE + PASSED live (WT b127): write-side conjunctive {end_user,agent_self} scoping + read-side cross- character isolation both proven end-to-end; betty (throwaway) deleted, Sindra intact. Full record in persistent-memory.d/2026-07-18-368-silo- test-passed.md. Retired the stale "silo test in progress" in-flight blocks. - Two-tier migration: split 152 over-threshold dated entries into persistent-memory.d/ detail files, leaving one-line pointers in the index (startup load ~196KB -> ~53KB; bodies now load on demand). - Tier-3 stores scrubbed clean (memory 0 / affect 0, provider restarted empty); persistent-memory + detail file updated to reflect the scrub.
866 B
[2026-07-01] LEDGER CORRECTION: #11 (AdminEvents) is NO LONGER BLOCKED. Verified via GET /me on :8081 that RATATOSKR_ADMIN_API_KEY (ratatoskr-readonly, tier readonly-admin) carries ALL 7 read scopes INCLUDING admin.events.read (+ admin.sessions.read, admin.keys.read, admin.skuld.read, pending.read, search.read, tool_events.read). The coverage-map + prior memory had #11 "blocked on admin.events.read" — STALE; the admin key was minted (post-#11-filing, env.sh) WITH the scope, so the blocker is already satisfied. Only the AdminEvents SSE pane itself is unbuilt — the last unbuilt §5 debug pane (a live SSE-consuming admin pane, distinct from the hydrate-at-attach panes). Coverage-map updated. Coverage: REST 11/40 ✅. Consider building the AdminEvents pane and/or updating #11's tracker status (its stated blocker is gone).