Skip to content

suite: --bindings reports which delegated invariants repos bind - #23

Closed
csecrestjr wants to merge 1 commit into
mainfrom
suite/bindings-report
Closed

csecrestjr wants to merge 1 commit into
mainfrom
suite/bindings-report

Conversation

@csecrestjr

Copy link
Copy Markdown
Contributor

Adds --bindings REPO [REPO ...] to jfa-conformance-suite.py.

It scans sibling repos' test files for TestInvariant__ functions (Go and JS/TS) and marks each implementation invariant they cite as BOUND — the binding P1-001 §9.14(b) defines. It does not run those tests: pass/fail stays with each repo's CI, so nothing is reported as passing (§9.15). Instrument- and document-bound citations are listed, not counted. A citation of an unregistered ID fails the run. Standard library only, offline.

The plain run is unchanged (byte-identical output), so the Conformance check and pre-push hook are unaffected. This is suite maintenance under §9.17: no registry ID, anchor or binding changes.

Against Cloudy main: 7 of 23 implementation-bound invariants bound; 20 of 27 delegated remain self-attested.

Not included: running --bindings in Janus CI (it's a required check, and a cross-repo checkout would let another repo's typo block Janus). Suggest that for Phase 3.

Noticed, not changed: CONTRIBUTING.md says twenty-five invariants are anchored; the registry now has thirty.

Signed-off-by: Calvin Secrest <dev@calvinsecrest.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant