gmira-verifylisted

# Verify The gate. Nothing goes back to the user without this, and the last step is looking with your own eyes. Load `../gmira/references/DOCTRINE.md` (Part 7.3 is the budget, Part 8 is the gate table). ## The budget **Two screenshot rounds, fixes batched between them.** Round one collects every finding across every viewport. Round two confirms the batch. A third round means the direction was wrong, not the details. Go back to `gmira-direction` rather than iterating on pixels. Per-tweak screenshot loops burn the user's budget and converge on nothing. ## The five viewports Fixed, and they are not negotiable. They are the ones where the predecessor project's regressions actually appeared. ``` 1920x1080 desktop wide 1440x900 desktop, the design default 1024x768 small laptop and landscape tablet 834x1112 tablet portrait 390x844 phone ``` ## Run it ```bash node skills/gmira-verify/scripts/verify.mjs http://localhost:3000/route --out proofs/<slug> ``` The script writes one screenshot per viewport, a `report.json`, and a `report.md`. It collects console errors, computed contrast failures, text overflow, missing focus styles, and canvas health. It cannot judge. That part is yours, below. ## The anchoring quarantine **Do the taste read first, in isolation, and write it down before opening the report.** When you have both a deterministic checker and a judgment pass, the checker's output becomes the ceiling of the judgment: once the machine's list is satisf