Checks
The console runs the verifiers in ci/ and shows what they say.
It owns no rules of its own — a second implementation of "is this legal" is two answers to one
question. A verifier that expects a pull-request context will fail here, and that is honest
rather than a bug.
Waiting for a subject. These verifiers grade one pull request, not the repository. Add
?task=<id> (and &tier=T0) to run them against a real task.| state | verifier | checks | output |
|---|---|---|---|
| needs-context | ci/verify-artifact-chain.js |
every task carries the artifacts its tier requires | verify-artifact-chain: no task id given — pass one positionally or set TASK_ID. Cannot evaluate. |
| needs-context | ci/verify-provenance.js |
enforces R1 — receipt, registered host, signed commits | verify-provenance: no task id given — pass one positionally or set TASK_ID. Cannot evaluate. |
| needs-context | ci/sensitive-paths.sh |
R3 — auth, billing, migrations and permission logic | sensitive-paths: no task id given — pass one positionally or set TASK_ID. Cannot evaluate. |
| needs-context | ci/verify-diff-size.sh |
the per-tier diff cap | verify-diff-size: no tier given — pass one positionally or set TIER. Cannot evaluate. |