Documentation
¶
Overview ¶
Command schemagen derives the checked-in JSON Schema 2020-12 documents that back the provider conformance gate.
It reads the four official upstream API descriptions, converts each one from its own dialect into standalone 2020-12 documents (one per api-format and message kind, with every reference rebased into a local $defs so the documents validate offline), and writes them plus an index, a provenance record and a report of everything the derived schemas do not enforce.
Refresh path (the only supported way to regenerate; never hand-edit the output):
go run ./codec/conformance/cmd/schemagen \
-fetch -specs /tmp/looprig-inference-conformance-specs \
-out codec/conformance/schema
-fetch downloads each source from the URL recorded in provenance.json before converting. Without it the tool converts whatever is already in -specs, which keeps regeneration reproducible offline. Either way the resulting tree is committed as-is: upstream drift shows up as a git diff, and the SHA-256 of every source document (plus a key-sorted canonical hash, for sources whose byte encoding is not stable) is recorded in provenance.json.