Skill: Fix design notes

PR CI no longer runs the design review (the judge-vision job was removed). Get the notes locally: record the spec, then pnpm --dir evals design:review -- --test-run latest. Older PRs may still show notes in their Evidence preview check.

Every PR that records evidence screenshots gets an advisory design review. Its notes ride in the Evidence preview check, next to the evidence they are about: one summary line, and the notes as the check's text. They never change the evidence verdict, but a note marked Worth fixing is a defect a careful designer would send back. Fix it, or say in the PR why the screen is right.

Read the notes

sha=$(gh pr view <pr> --json headRefOid --jq .headRefOid)
check() { gh api "repos/{owner}/{repo}/commits/$sha/check-runs?check_name=Evidence%20preview" --jq ".check_runs[0].output.$1"; }
check summary   # ends with "Design review (advisory): 3 notes, 1 worth fixing." or "no notes."
check text      # the notes, then the same notes as JSON

Each note gives:

Field	Use it to
rule	layout.* was measured from the DOM (exact). S2, V2… are DESIGN.md; OW-* are the OpenWork Design rules in evals/design-review/rubric.md (judged from pixels; may vary run to run)
Screenshot	the spec step that took it, and the spec file
Where in the code	grep for the hook ([data-library-row="…"] → data-library-row) or the class list to find the component
Reproduce	the command that re-records the screenshots and reviews them locally

The JSON block at the end of the check text has the same notes for scripts. The screenshots themselves are in the review report the check links to.

Reproduce, fix, verify