Skip to content

Keep Memory indexes current across write paths (#442) - #498

Merged
possiblyneal merged 1 commit into
mainfrom
fix/442-memory-write-indexing
Nov 21, 2026
Merged

possiblyneal merged 1 commit into
mainfrom
fix/442-memory-write-indexing

Conversation

@possiblyneal

Copy link
Copy Markdown
Owner

Intent

Closes #442

Keep the live Memory indexes current before a restart, including when heal or mesh supersedes a Memory.

Read first

  • src/functions/diagnostics.ts and src/functions/mesh.ts — shared Memory lock and index updates.
  • test/memory-write-indexing.test.ts — smart-search regressions.

Decisions

  • Heal rechecks the stored supersession edge under the same lock as mesh. Mesh keeps last-write-wins.
  • Auto-page creates an archive, not a successor; its smart-search fixture is unscoped.

Out of scope

  • Changing auto-page ownership or search ranking.

Verified

  • CI=1 npm test -- test/memory-write-indexing.test.ts test/mesh.test.ts test/supersession.test.ts test/diagnostics.test.ts → 109 passed.
  • Full local gate → 3,273 passed, one skipped; build, generated hooks, skills, typecheck and both Recall gates passed. Independent review signed off on the staged tree.

Not verified

  • No live store or embedding provider was used.

Merge danger

Door: Revertible code; no schema change or migration.

Blast radius: Live Memory indexing from consolidation, auto-page, heal, mesh receive and mesh sync.

@possiblyneal
possiblyneal merged commit 5528ed8 into main Nov 21, 2026
3 checks passed
@possiblyneal
possiblyneal deleted the fix/442-memory-write-indexing branch November 21, 2026 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Consolidate, auto-page, heal and mesh sync write Memories without updating the search index

1 participant