It is supplied, not authored: it is staged verbatim into the build directory, hash-verified against the import, and restored before grading. Run the upstream jq conformance corpus against a candidate implementation. This runner re-implements the corpus protocol and drives the candidate as a subprocess, one process per case. Its exit status is the acceptance verdict. Parse the jq test corpus. An exclusion that matches nothing is a hard error rather than a shrug. Structural, not textual: ``1`` and ``1.0`` are the same jq value and the corpus relies on that. A case that has not produced output in this long is not going to. run only cases whose program matches REGEX jq conformance: {tally[PASS]} passed, {tally[FAIL]} failed, {tally[ERROR]} errored, {tally[SKIP]} skipped --json