### wai-quantum: a verdict for every answer, stable refusal codes, and repairs held to the flagged lines

Every answer an agent or a person gets about a program states one verification level, so "valid" is never the claim (`wai-quantum/docs/verdicts.md`).

- **The verdict** (`engine::verdict`): the level of an ordered ladder (`refused` < `parsed` < `executed` < `evidence` < `proof`), whether the intents hold, and the level in one plain line; with what the reader said (its codes), the method and its accuracy class, each intent's check, the critique's findings and the repairs made.
  - Intents: an exact distribution with its total variation distance (the state vector, or under noise the density matrix), the same circuit as a reference by the equivalence ladder (proof or evidence), the same state from |0…0⟩, or samples of the run held to a stated distribution by a stated test at a stated level (the debugger's `sampled` intent, now in the engine for every surface: evidence, never proof). `"require": "proof"` counts evidence as unchecked.
  - A run on a device target states its verdict too: its intents checked on the program, a sampled intent on samples of the target's run.
  - A job asks with `"intent"` or `"verdict": true`, and its result carries the verdict, sealed by the receipt; the plan admits the check's memory. A job that asks for neither gives the bytes it gave before (pinned against the engine before this change).
  - The checker `wai-quantum test` used moved into the engine, and `test` now runs the program with its intents; `--junit` reads the engine's verdict.
- **Stable refusal codes for what is asked of a program** (`engine::refusal`, `docs/job-refusals.md`): the request (`J001`–`J006`), the method (`J010`–`J012`), intents and repairs (`J020`–`J022`) and the host (`J030`–`J032`), each refused or retry, beside the reader's `Q` codes. A refusal ends with its code, a reader's cause before it (`[Q500] [J011]`); the service's HTTP refusals carry it as `code`.
- **Repairs** (`engine::repair`): the fixes that are mechanical, each on the lines its diagnostic flags (a missing `;`, an undeclared register's size, a measurement with no target, an unbounded `while` given its bound, a non-dyadic angle rounded to the bits chosen with its rounding stated); a proposal that changes any other line rejected (`J021`); what needs a person returned with the reader's advice. A job may ask to be repaired first.
- **Surfaces**:
  - the command line: `run --intent FILE` (a reference program, a distribution, intents, or `intent.json`), `--verdict`, `--repair`, and `repair FILE` (`--proposed`, `--max-iterations`, `--dyadic-bits`, `--size`);
  - both MCP servers: `intent` and `repair` on `run_quantum_circuit`, which always states its verdict; the tool `repair_qasm`; the verdict in every answer about a program and the codes in every refusal; versioned output schemas on every tool; the resource `wai-quantum://docs/verdicts`; the rules and prompts point agents at the verdict and `repair_qasm`, and the generated agent docs and the Agent Skill say so;
  - the service: intents and repairs in jobs, held to the equivalence bound; `POST /v1/repair`;
  - the Studio and the desktop app: a badge with the level on every run and every assistant proposal;
  - the browser engine: `engine_verdict` and `engine_repair`;
  - Python: `run(..., intent=...)`, `Job.verdict`, `wai_quantum.verdict` and `wai_quantum.repair`.
- **Conformance** (`quantum-conformance/intents/`): programs, their intents and the verdict each must get, every level covered and the distances known by hand, run natively and under `wasm32-wasip2` (`wai-quantum-verdict.yml`) and in the browser build (`wai-web-wasm.yml`).
