feat: add v1.0 reliability features — lockfile, backup, recovery, integrity#48
Merged
keeganthomp merged 2 commits intomainfrom Apr 8, 2026
Merged
feat: add v1.0 reliability features — lockfile, backup, recovery, integrity#48keeganthomp merged 2 commits intomainfrom
keeganthomp merged 2 commits intomainfrom
Conversation
…egrity Implement all four reliability items from the v1.0 roadmap: - Lockfile mechanism (.kb/vault.lock) prevents concurrent vault writes with stale lock detection, re-entrant support, and PID-based ownership - Automatic backup creates manifest snapshots in .kb/backups/ before destructive operations (compile --force), with pruning to keep last 5 - Crash recovery detects incomplete writes (.tmp files), stale locks, corrupt manifests, and repairs them (including restore from backup) - Manifest integrity validation checks source/article files exist on disk, cross-references are consistent, and stats match reality Compile, ingest, and lint --fix are now wrapped with vault locks. 40 new tests, all 394 tests passing. https://claude.ai/code/session_0127AhEBpSs1q8CgtNCRAwCW
Documentation suite: - docs/getting-started.md — quick start tutorial with real examples - docs/vault-format.md — complete vault structure and schema spec - docs/skill-authoring.md — guide to creating custom skills - docs/provider-config.md — LLM provider setup and model config - docs/architecture.md — codebase architecture for contributors Testing & quality: - E2E test: full init → ingest → compile → search → query → lint lifecycle - Performance benchmarks: vault init, manifest load, search build/query, ingest throughput, compile no-op latency - Coverage reporting via `bun test:coverage` - Fix integrity validator to correctly derive source file paths from metadata title (source IDs are hash-based, not file paths) 402 tests passing, all lint clean. https://claude.ai/code/session_0127AhEBpSs1q8CgtNCRAwCW
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
2 participants
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.
Implement all four reliability items from the v1.0 roadmap:
with stale lock detection, re-entrant support, and PID-based ownership
destructive operations (compile --force), with pruning to keep last 5
corrupt manifests, and repairs them (including restore from backup)
disk, cross-references are consistent, and stats match reality
Compile, ingest, and lint --fix are now wrapped with vault locks.
40 new tests, all 394 tests passing.
https://claude.ai/code/session_0127AhEBpSs1q8CgtNCRAwCW