Chio/Docs
LOGIN · JOIN

chio conformance

Run the cross-language conformance harness against a peer adapter, and fetch the peer adapters it runs against.

Reference chio@5f63e6e

On this page

All command families · Global flags

chio conformance

Run the cross-language conformance harness against a peer adapter.

Command synopsistext
chio conformance [OPTIONS] <COMMAND>

chio conformance run

Execute conformance scenarios against a peer language adapter.

Command synopsistext
chio conformance run [OPTIONS] --peer <PEER>
  • --peer <PEER> Peer language adapter to exercise (js, python, go, cpp, or all). Required.
  • --report <REPORT> Optional report format. Pass json to emit machine-readable JSON summarising the run; omit to print a human-readable summary.
  • --scenario <SCENARIO> Optional scenario id filter. When set, only scenarios with this id are surfaced in the printed/written report; the underlying harness still executes the full corpus.
  • --output <OUTPUT> Optional output file. When provided, the report is written to this path; otherwise the report is printed to stdout.
  • --peer-binary <PATH> Explicit peer executable to run. Valid only with a single --peer language, and used by release smoke tests after fetch-peers downloads a pinned artifact.

chio conformance fetch-peers

Download pre-built peer-language adapter binaries pinned in crates/tooling/chio-conformance/peers.lock.toml.

Command synopsistext
chio conformance fetch-peers [OPTIONS]
  • --check Verify the lockfile shape only; do not download anything.
  • --out <OUT> Output directory for fetched binaries. Default ./.chio-peers.
  • --language <LANGUAGE> Optional language filter (python, js, go, cpp).
  • --allow-unpublished-only Allow a selection whose matching peers are all published = false. This is only for workflows before publication that validate lockfile shape before release assets exist; normal fetches fail closed.
  • --lockfile <LOCKFILE> Optional explicit path to peers.lock.toml. When omitted the CLI consults $CHIO_PEERS_LOCK, the XDG config dir, the in-repo path, and the cwd in that order.

Read more in Compatibility and evidence.