What problem does it solve? Static checks cannot catch runtime failures like a stale server serving yesterday's build, horizontal overflow at 320px, console errors on load, or keyboard focus traps. This Skill serves the built frontend and verifies its actual runtime behavior before a slice is closed, producing evidence-backed PASS/FAIL/BLOCKED verdicts instead of unverified claims. ## Core Features & Use Cases - Page identity assertion with recovery: Asserts the served page is the right one before any other check, automatically re-binding to a fresh free port on a collision or stale server. - Runtime verification battery: Probes horizontal overflow at 320/768/1280/2560 px, walks keyboard focus, captures console errors, and runs Lighthouse and axe when available, reporting honest n/a when tools are absent. - Evidence-based gate decision: Classifies findings with a taxonomy (CONSOLE_ERROR, OVERFLOW, FOCUS_DEFECT, etc.), writes a WEB_RUNTIME_VERIFY.md report with screenshots, and routes failures to the appropriate fix command. - Use Case: After implementing a responsive pricing page slice, run this gate to confirm the built page loads without console errors, shows no overflow at mobile widths, and passes its acceptance criteria before closing the slice. ## Quick Start Verify the runtime behavior of my built frontend in the dist folder against the slice's acceptance criteria and give me a PASS or FAIL verdict.
