fix: classify schema-11 databases as upgradable behind-schema state#124
Merged
Conversation
- route versions between the journal-first ceremony and the current baseline to the behind-schema classifier; alpha.10 reported schema-11 databases invalid with no forward path - accept the optional journal-first row in the classifier and require exactly the auto-applied migrations at or below the recorded version, covering both fresh and journal-first schema-11 shapes - falsified with schema-11 fixtures for both shapes and proven against a copy of a real alpha.9 database: typed upgrade guidance, dry-run, backup-first apply to schema 12, and working journal reads afterward - refresh installed smoke evidence for the rebuilt binary
levifig
added a commit
that referenced
this pull request
Jul 19, 2026
Hotfix prerelease publishing the schema-11 upgrade-classification fix (#124): version files to 2.0.0-alpha.11, curated changelog fold, stamped artifact rebuild, and refreshed installed smoke evidence.
levifig
added a commit
that referenced
this pull request
Jul 19, 2026
…the foundation ship (#126) Reflect updates from the foundation ship: adversarial review recommended for foundational state-model changes (PR #122 evidence: thirteen Codex findings after two Claude reviews), and one explicit fixture per supported starting state for migration/classification code (the alpha.10 transitive-coverage regression, #124).
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
1 participant
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.
v2.0.0-alpha.10 reports every schema-11 database (all v2.0.0-alpha.9 installations) as invalid with no forward path: the upgrade classifier only recognized versions below 10 and exactly 10 as behind-schema, and the classifier itself rejected both legitimate schema-11 shapes.
loaf state migrate schema --applyguidance, non-mutating dry-run, backup-first apply to schema 12, working journal afterward.Follow-up prerelease v2.0.0-alpha.11 will publish this immediately; alpha.10 should be considered unusable for existing installations.