fix(compat): close semantic lineages and remediate recovery - #59
Merged
Conversation
This was referenced Aug 26, 2026
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
(AppliedVersion, Signature).schema_migrationsprovenance from semantic hashing while preserving ledger validation and migration planning.OpenCompatibleto the exact current head with zero skips.recoveras remediation: retain the mutation-grade startup lease while bypassing ordinary compatible-open and pre-handler sync.Why
ALTER-built V13 databases produced valid but unrecognized V14 signatures, causing every operational command—and
recover --dry-runitself—to fail withunsupported_lineage/migration_failed.This closes the defect class rather than adding V14-specific signature exceptions.
Closes #58.
How
remediationstartup classification, immediate/busy-owner lease tests, real ALTER-built recovery dry-run immutability, and repeated subprocess contention coverage.Verification
TestEveryCatalogFixtureReachesCurrentSemanticHead: 19/19 fixtures PASS, zero skips.recover --dry-run: PASS; no circular diagnostics; DB and empty WAL unchanged..backup; original database hash unchanged.-count=5; sync counter remains exactly 1.internal/startuplockcompile: PASS.just ci: PASS, aggregate coverage 86.1%.No new flag, command, lock type, fallback catalog, repair mode, persistent application state, V14 runtime exception, or migration SQL change was added.
Checklist
just test)just check)cargo insta review) — not applicable