The acceptance fixture matrix
tooldocstest.dev ships with five acceptance fixtures that together form the product's release gate (PRODUCT.md, "Exact acceptance gate"): an outdated argument example must fail, a current example must pass without production credentials, and malformed, missing-data and adversarial inputs must never be certified as a pass. Each fixture is run through the real local CLI; the result and exit code below are exactly what that run produces, and a regression test fails the build if the two ever diverge.
The five fixtures
| Category | Fixture | Result | Exit code | What it proves |
|---|---|---|---|---|
| positive | fixtures/passing.json |
pass | 0 | A current quickstart example executes through an allowlisted, data-only sandbox tool and matches the contract. |
| negative | fixtures/failed.json |
fail | 1 | An outdated argument name no longer satisfies the tool schema, so the example fails the contract check without the tool being called. |
| missing-data | fixtures/missing-data.json |
fail | 1 | A required argument is absent, so the example fails the schema check. |
| malformed | fixtures/malformed.json |
unknown | 2 | An invalid envelope cannot be evaluated and is rejected as unknown, never reported as a pass. |
| adversarial | fixtures/adversarial.json |
unknown | 2 | A forged, loosened schema does not match the built-in sandbox tool definition, so the example stays unknown and is never certified. |
Reproduce it
Each row is one CLI invocation. The receipt is deterministic and never echoes the example payload values:
node src/cli.mjs fixtures/passing.json # pass, exit 0
node src/cli.mjs fixtures/failed.json # fail, exit 1
node src/cli.mjs fixtures/missing-data.json # fail, exit 1
node src/cli.mjs fixtures/malformed.json # unknown, exit 2
node src/cli.mjs fixtures/adversarial.json # unknown, exit 2
Exit codes follow the tri-state convention: 0 pass, 1 fail, 2 unknown or invalid input. Unknown is distinct from both pass and fail; a schema that cannot be evaluated, or a forged contract that does not match a built-in sandbox tool, stays unknown rather than being reported as a pass.
For the full input contract and adapter limits see the documentation, or go back to the overview.