Documentation
¶
Overview ¶
Command memql-bench runs the proving corpus and publishes what it measured.
It ADOPTS THE CAPABILITY-SCRIPT CONTRACT (docs/internal/design/capability-script-contract.md): `--flag=value` in, one JSON envelope on stdout, every human line on stderr, `--print-spec`, and the contract's exit codes. `scripts/lib/capability_contract_test.go` walks `scripts/**/*.sh` and will never see a Go binary, so what stands behind that claim is component/proving/capability -- whose test reads the printf format strings out of `scripts/lib/capability.sh` and fails when the two drift -- plus the `proving` CI job, which parses this binary's envelope.
Subcommands are selected by --do, not by a positional verb: the contract takes no positional arguments, and a verb in argv[1] is exactly the position-dependent parameter a machine caller gets wrong.