---
description: Run the objective gates and report evidence, not opinions
---

Run `./scripts/verify.sh` and report the result.

Then, if the working tree has uncommitted changes, produce feature-specific evidence for what
changed: start the server and `curl` the affected URL, run the relevant test by name, or diff
the golden file. Show real output.

If anything fails:
1. Report the failure verbatim before interpreting it.
2. Diagnose in one paragraph.
3. Propose the smallest fix. Do not apply it without a go-ahead unless it is a formatting fix.

If a budget in `scripts/budgets.env` is exceeded, do not raise the budget. Report which budget,
by how much, and which files are responsible. Offer the two options: shrink the code, or an ADR
raising the ceiling deliberately.