Repository navigation
corpus: read entries from locks/schema-<N>/ (DSE-2143) - #124
Merged
Merged
Conversation
The community corpus is append-only and locks/<eco>/<segment>/<version>/<attester>.lock had no slot for a second lock schema of one coordinate, so every schema-3 entry written by 1.x made 2.x fail closed with WRD-CONSENSUS-SCHEMA-MISMATCH. Coordinate.relative_dir() now prefixes locks/schema-<SCHEMA_VERSION>/; legacy entries are never read (NOVEL). Fixture corpus moved, new regression test, COMMUNITY_CORPUS.md section 4, CHANGELOG.
Merged
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.
Consumer half of DSE-2143 (option 2, approved by Ernest 2026-10-24).
Coordinate.relative_dir()→locks/schema-<SCHEMA_VERSION>/<eco>/<segment>/<version>(CORPUS_SCHEMA_DIR, todayschema-4).locks/<eco>/...are never read: NOVEL instead of the current fail-closedWRD-CONSENSUS-SCHEMA-MISMATCHthat breaks every 2.x consumer.schema_versiondisagrees with its subtree still fails closed (unchanged check).locks/schema-4/;gen_corpus.pyuses the constant; new testtest_legacy_layout_entries_are_never_read.Builder: 1530 passed, 7 skipped.
Follow-ups: release 2.2.0; mcp-warden-locks writes new entries under
locks/schema-4/and re-attests all coordinates.