Repository navigation
docs(project): refresh conformance records to the current develop head - #1034
Merged
Merged
Conversation
Re-measure the roadmap's gate table at develop (42b5485, four days past v0.9.2) with the v0.9.1 figures kept in brackets, regenerate the grammar coverage baseline over the current local corpora, and correct the README's standard-library prose to the 110 files the parser gate reads. Co-Authored-By: jason.han <hanhuijun@gmail.com>
Contributor
Author
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
Contributor
Author
There was a problem hiding this comment.
🔍 Devin Review: 2 flags
Not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)
… head Re-measure the roadmap gate table on develop one day past v0.10.0, fold the Test-function counts into the table and drop the stale paragraph that still described the v0.9.1 head; regenerate the grammar-coverage input census. Co-Authored-By: jason.han <hanhuijun@gmail.com>
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 and why
An audit of every conformance record under
docs/project/against a fresh run of its gate ondevelop, first at42b54859fand re-run at687d6f501(one day pastv0.10.0). Every CI-gated baseline — Xpect, pilot differential, rejection, PSSM referee, fUML referee, validation census, transformation census, documentation counts, the five corpus gates, library-XMI identity, execution conformance and the gRPC conformance suite — reproduces its committed figures unchanged. Three records had drifted and are refreshed here:docs/project/roadmap.md— the "Where the repository stands" gate table was still thev0.9.1measurement. It is re-measured at thedevelophead one day pastv0.10.0, with thev0.9.1figure kept in brackets where it moved (pilot corpora 9 → 16 files reporting, stdlib 107 → 110, execution conformance 1224 → 1490, rejection oracle 310 → 313 cases, validation census 158/6 → 155/9 faithful/approximate, PSSM 60/12/30/1 → 56/6/34/7, the execution-conformance case, golden-trace and robustness counts, RDF and API round trips 358 → 365 models, and the test-suite inventory). TheTest-function counts move from the prose into the table, and the paragraph that still described thev0.9.1head (311 rejection models, PSSM 52/12) is replaced by one stating that nothing between thev0.10.0tag and thedevelophead is a gate input.docs/project/grammar-coverage-baseline.json— the advisory grammar-production census's input figures (file and line counts of the local corpora it reads) lagged the tree; regenerated withgo run -C tools ./cmd/grammar-coverage -baseline …. No production-coverage row moved.README.md— the "Completeness" bullet still read 105 of 105 standard library files with 11 extensions; the parser gate reads 110 (94 vendored OMG files, 16 OpenSysML extensions), as the README's own parser-coverage paragraph already states.No implementation changed; the pinned oracle inputs were re-fetched at their pins and every movement above is the tree growing, not a conformance movement.
How it was verified
go run -C tools ./cmd/pilot-xpect -check,pilot-diff -check,pilot-reject -check,pssm-referee -check,fuml-referee -check,validation-census -check,transformation-census -check— all agree with their committed baselines.go test -count=1 ./tests/corpus ./tests/identitywith the require variables set (training 100/100, pilot corpora, PSSM migration, RDF and API round trips, library XMI) — pass.make conformance,go test ./internal/exec/runtime -run 'TestExecutionConformance|TestExecutionTrace'— pass.make docs-counts,make docs-check,python3 scripts/check-doc-ids.py,make ontology-table-check,make stdlib-snapshot-check,go test -C tools ./census/grammar/...— pass.go run -C tools ./cmd/doc-counts -site-blockson this tree.Checklist
make testandmake lintpass locally (documentation-only change; the gates above were run)make docs-countsrun if a gate count moved