feat: prepare v1.5.0 trust and indexing foundation #21
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.
Summary
What is included in this PR
src/preflight/evidence-lock.ts, preflight integration insrc/index.tssrc/memory/store.ts, git memory extraction insrc/memory/git-memory.tssrc/core/manifest.ts, indexer integration insrc/core/indexer.tssrc/types/index.ts,src/storage/types.ts,src/storage/lancedb.ts, constantsmemory.datenow evaluates as stale evidence (commit5fa2040)Validation
pnpm lint✅pnpm format:check✅pnpm test -- tests/confidence-decay.test.ts✅Notes on docs/changelog split
v1.5.0/docs-facelift) to keep this foundation PR focused on core behavior and testability.README.md,MOTIVATION.md,AGENTS.md) but the final release messaging pass is in docs: align release notes with shipped search and incremental behavior #23.Why this split