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.
790 B
[2026-07-13] A same-image redeploy does NOT reload a bind-mounted config — the ModelRegistry boot-caches it at __init__. After the config was synced on-disk (infra-ops validated) and docker compose up -d re-ran, the reasoning-off change STILL didn't take: an unchanged image makes up -d a no-op (no container recreate), so the process kept serving the pre-sync config. Fix = a surgical docker restart <container> (same image, no pull) → the process re-boot-reads the config. When an on-disk config change doesn't take effect, suspect the process cached it at startup; force a container RESTART, not a redeploy (a docs-only forcing-commit also won't rebuild if docs are paths-ignored in CI). This is the config-plane sibling of the [2026-07-06] stale-image foot-gun.