You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Consolidate, auto-page, heal and mesh sync write Memories without updating the search index #442
Not verified on this tree yet. Held at needs-triage until Verify: four write paths skip the search index gives a tested verdict: a failing reproduction and a fix that works here, or a reject.
Tested on verify/442-index-writes (from fdc3d459), per the bar in #449.
Repro.test/memory-write-indexing.test.ts fails 4/4 on base. Four paths write a Memory without touching the live index, so until the next restart a new Memory is invisible to smart-search and prompt-context and a superseded one still ranks:
mem::consolidate, no-predecessor branch: new Memory not indexed
mem::auto-page: paged Memory not indexed
mem::heal: sets isLatest: false, id stays indexed
mem::mesh-receive / applySyncData: a received latest Memory is not indexed, a received closed one is not de-indexed
Fix.indexNewMemoryVersion() after the consolidate and auto-page writes, deindexSupersededMemory() after heal, and a reindexMergedMemory hook passed as lwwMergeList's onWrite for both mesh merges. deindexSupersededMemory also drops chunk vectors (VectorIndex.remove clears id#*). docs/supersession.md and the CLAUDE.md De-indexing rule list the new paths.
Checks.npm run typecheck 0 errors; npm test 3120 passed, 1 skipped; eval:gate and eval:gate:rules pass; eval:suite --tier fast vs base-fdc3d459: every metric Δ 0.000.
Operator's data. None of the four paths has written a Memory on the live store (0 audit entries; all 42 Memories came from remember). Correctness only.
Activity
possiblyneal commentedon Nov 18, 2026
Not verified on this tree yet. Held at
needs-triageuntil Verify: four write paths skip the search index gives a tested verdict: a failing reproduction and a fix that works here, or a reject.possiblyneal commentedon Nov 18, 2026
Verdict: apply (latent)
Tested on
verify/442-index-writes(fromfdc3d459), per the bar in #449.Repro.
test/memory-write-indexing.test.tsfails 4/4 on base. Four paths write a Memory without touching the live index, so until the next restart a new Memory is invisible to smart-search and prompt-context and a superseded one still ranks:mem::consolidate, no-predecessor branch: new Memory not indexedmem::auto-page: paged Memory not indexedmem::heal: setsisLatest: false, id stays indexedmem::mesh-receive/applySyncData: a received latest Memory is not indexed, a received closed one is not de-indexedFix.
indexNewMemoryVersion()after the consolidate and auto-page writes,deindexSupersededMemory()after heal, and areindexMergedMemoryhook passed aslwwMergeList'sonWritefor both mesh merges.deindexSupersededMemoryalso drops chunk vectors (VectorIndex.removeclearsid#*).docs/supersession.mdand the CLAUDE.md De-indexing rule list the new paths.Checks.
npm run typecheck0 errors;npm test3120 passed, 1 skipped;eval:gateandeval:gate:rulespass;eval:suite --tier fastvsbase-fdc3d459: every metric Δ 0.000.Operator's data. None of the four paths has written a Memory on the live store (0 audit entries; all 42 Memories came from
remember). Correctness only.Merge pull request #498 from possiblyneal/fix/442-memory-write-indexing