Repository navigation
feat: add private durable lineage storage - #8
Merged
Merged
Conversation
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.
Interrupted migrations need durable evidence without persisting conversation content or treating a recovered record as permission to publish again. Add a private stdlib lineage storage API with an exact schema, qualified identities, separate hashes/checkpoints and conservative reconciliation receipts.
SQLite operates only in memory; validated file descriptors and atomic image replacement persist state under persistent namespace/store locks. Volatile guard claims distinguish a live prepared operation from recovered
readymetadata. Locks, image/record limits, reserved finalization capacity, namespace substitution, crash boundaries and unknown schemas fail closed.This is the storage component of the lineage milestone. Canonical projection, operation integration, continuity commands and the dashboard remain separate work. CLI/TUI transfer behavior is unchanged. It does not add in-place native update, external harness exclusion, automatic replay or database migrations.
Validation: independent storage review approved67/0 plus restore/readonly/foreign-lock probes; full core2215 passed/57 optional-native or extra prerequisite skips; installed wheel80 passed/0 skips with all Python/TCSS bytes verified and core-only lazy import; Ruff check/format197, diff/build and uv lock16 passed. Python3.11–3.13 and designated native jobs must pass in remote CI. All storage tests use synthetic private fixtures; no real native sessions or authentication data are read.