- #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.
1.7 KiB
[2026-06-30] Finding P-1 (pin drift) + pin-remediation PENDING. We vendor the PROSE markdown (docs/conversation-api-spec.md), which is byte-identical to live WT's but frozen at v0.35.16-era content (last WT edit 2026-05-31) — it does NOT capture b2: 7 new endpoints (admin/keys/bulk, admin/persona/{archive,erase}, admin/usage, embed, judgments, me/usage), the 409/503 on messages-POST (#331), the unified error envelope (#328), or the SSE schema. WT's authoritative v1 truth is now the FROZEN OpenAPI 2.2.0 + SSE-schema JSON (Worldtree/docs/v1-schema-freeze-manifest.md). So the previously-deferred "re-vendor markdown to b2" is a near-no-op (markdown content identical). Pending operator nod: re-pin to the machine-readable artifacts (recommended — drift-checkable via canonical_drift.py, makes the coverage map reproducible vs a frozen diffable target) vs markdown-only. Deferred (not auto-applied) because it adds vendored artifacts + a canonical-sync pin = substrate change with CI-gating reach. → RESOLVED 2026-06-30 (operator: "a then b"). Vendored conversation-api-openapi.json (2.2.0) + conversation-api-sse-events.schema.json + re-copied the prose markdown; pinned all three in .corviduo-canonicals.toml (OpenAPI+SSE = strict drift gates, markdown = tolerate_drift reference); advanced worldtree-spec-rev f1b59f8→5810a26 + worldtree-version v0.29.0(STALE, never bumped from the v0.35.16 pin)→v1.0.0b2 + pinned-on→2026-06-30; SPEC-PIN.md history row added. canonical_drift.py green (10/10). pin:-only, no version bump (no client-facing code change; the b2 409/503 + error-envelope were already consumed in v0.18.3/.4).