feat: add a schema for machine-readable provider conformance reports - #425

Draft

aepfli wants to merge 15 commits into

feat/provider-tck-appendix-docfrom

feat/provider-tck-report-schema

Commits on Oct 1, 2026

feat: add a schema for machine-readable provider conformance reports
aepfli
committed
ce5aac1
feat: identify executed assets by git tree hash rather than a content digest
aepfli
committed
9990dde
feat: enforce reasons, and let a single scenario carry a known deviation
aepfli
committed
bc5fd34
feat: identify a Scenario Outline row by its parameters
aepfli
committed
66c8a0e
docs: state that example key order is not significant
aepfli
committed
99c9d96
feat: carry results in Cucumber Messages instead of defining our own
aepfli
committed
30b9c37
feat: record which version of the results format was produced
aepfli
committed
c61d17e
docs: correct what specRevision alone has to carry, and how to read a stream
aepfli
committed
d9899cf
feat: a capability the suite does not test must not be declared
aepfli
committed
4fb1616
docs: rename the capability in the notApplicable illustration
aepfli
committed
6273fe3
feat: drop declaration.notApplicable, one skip carries its own reason
aepfli
committed
c23f6df
docs: say what the conformance report is, and what provenance is for
aepfli
committed
fdd2323
feat: require a deviation's summary, and stop implying its issue is mandatory
aepfli
committed
4d11582
feat: require backend.controlApi, which decides what the rest of the report is worth
aepfli
committed
7954b1f
fix: the declaration no longer explains every skip, and said it did
aepfli
committed
bac2bab