v0.30.0 — index self-heal (foreign writer + embeddings backfill) + MCP warm-on-boot - #5
Merged
Conversation
…ackfill Three index-integrity fixes: - Per-node `stamp` column: a foreign-version writer (old global CLI, stale node_modules) poisoning a SUBSET of files is now caught and re-chunked, which the whole-index user_version stamp structurally cannot see. - MCP warm-on-boot: fire-and-forget `ctx.index()` after the initialize handshake so an MCP-only host (no session hook) never recalls against an empty/stale index. Opt out with LITECTX_NO_WARM_INDEX. - Embeddings backfill: a file indexed while the tier was OFF (library default) gets its vector on a later ON pass, instead of the content-diff fast-skipping it and leaving semantic recall silently dead. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014c3EffnCPFetsv41LhZcJx
…ill), MCP warm-on-boot Version bump + docs (CHANGELOG, litectx.context.md MCP section, PRD self-heal section). Feature commit is eb63955. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014c3EffnCPFetsv41LhZcJx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Three index-integrity fixes, released as v0.30.0.
Added
index()right after theinitializehandshake — fire-and-forget (the handshake never waits), rejections logged to stderr (never the JSON-RPC stdout stream). Opt out withLITECTX_NO_WARM_INDEX.Fixed
PRAGMA user_versionstamp (0.29.0) is blind to a different writer (old global CLI, stalenode_modules) re-chunking some files — it never touchesuser_version. Each node now carries the stamp of the litectx that wrote it (additivenodes.stamp,DEFAULT 0= "rebuild me"); a poisoned file self-identifies and re-chunks on the next unforced pass even when its bytes are unchanged. Existing indexes migrate on open.index()now embeds any indexed-but-vectorless file (read + embed only, no re-chunk), idempotently.Verification
node --test→ 409 pass / 0 fail / 1 env-skip, exit 0tsc --noEmit→ exit 0Scope
5 files (+167/−8 code) + docs (CHANGELOG,
litectx.context.md, PRD self-heal section).🤖 Generated with Claude Code
https://claude.ai/code/session_014c3EffnCPFetsv41LhZcJx