Repository navigation
conformance-suite: judge against the Core text it was transcribed from - #457
Merged
Merged
Conversation
The suite reads spec-core.md from the repository root and checks that every MUST sentence and every numbered Section 9 item is transcribed. The v0.1.0 lock rewrites spec-core.md, so those checks would fail until the catalogue and matrix are re-transcribed. Freeze a copy of spec-core.md at the commit the catalogue was transcribed from and point SPEC_SOURCE at it. Reports now name that copy and its version, so a result never claims to cover the locked text. Re-transcription against the locked text follows separately. Assisted-by: AI Signed-off-by: Tim Nunamaker <tnunamak@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
tnunamak
added a commit
that referenced
this pull request
Oct 27, 2026
Brings in the conformance-suite pin (#457) so the lock's CI runs against it. Assisted-by: AI Signed-off-by: Tim Nunamaker <tnunamak@gmail.com>
This branch was successfully deployed
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.
The conformance suite checks that every MUST sentence in
spec-core.mdand every numbered Section 9 item is transcribed inmatrix.tsandcatalog.ts. It readsspec-core.mdfrom the repository root. Merging the v0.1.0 lock (#374) rewrites that file: on main plus #374, 588 of 710 MUST sentences and 78 of 123 Section 9 items have no entry, sosuite vs reference implementationandtest-accounting:checkfail.This PR adds a frozen copy of
spec-core.mdatbabd0ef3fb(current main), the text the catalogue was transcribed from, aspackages/conformance-suite/spec/spec-core.md, and pointsSPEC_SOURCEand the two spec-reading tests at it.SPEC_SOURCE.versionnow reads "v0.1.0 public-review draft (3 September 2026)", so a report says which text it judged against and does not claim to cover the locked text.REUSE.tomlgives the copy the specification license.Re-transcribing the catalogue and matrix against the locked text is separate work. When it lands, it deletes the copy and sets
SPEC_SOURCE.pathback tospec-core.md.Verified: the suite's 356 tests pass on this branch alone and with
review/v0.1.0-revisionsmerged in;spec:checkpasses;reuse lintis compliant. No test file was added or removed.Assisted-by: AI