ui-verification

# UI Verification Owns the browser session. Every other UI skill in this repo reasons about source and infers what the user will see; this one loads the page and measures it. - **IS:** booting the app, driving it with a browser, and running the probes that decide a rule at runtime: computed boxes, injected failures, observed layout shift, a scripted Tab walk, an axe scan per theme. Output is findings keyed to rule ids with reproducible evidence, plus the clearing re-run after a fix. - **IS NOT:** finding defects by reading source or deciding their tier and ship verdict (`ui-design` Audit mode owns both); building or restyling UI (`ui-design` Build); authoring a durable test suite (write Playwright tests); pixel-diff regression against a baseline (Chromatic, Percy); field performance (RUM or CrUX; Lighthouse is a lab tool). The division of labour is the point. A static audit reports what the code will probably do; it cannot see a 40px control whose hit area a pseudo-element already expands to 44, or a retry button wired to nothing. This skill reproduces or kills each of those, so a finding arrives with a measurement instead of a confidence. ## Contents - [When to run](#when-to-run) - [Probe catalogue](#probe-catalogue) - [Progress checklist](#progress-checklist) - [1. Establish the session](#1-establish-the-session) - [2. Select the probe set](#2-select-the-probe-set) - [3. Run the probes](#3-run-the-probes) - [4. Decide each finding](#4-decide-each-finding) - [5. Clearin...