ABOUTME: End-to-end UI verification; never report a UI change done on a green edit or passing tests alone

ABOUTME: Browser interaction, zero-new-console-errors, before/after screenshots, Lighthouse gate when perf-relevant

Verify Frontend

A successful edit and green unit tests do NOT verify a UI change: they can encode the same wrong assumption as the code. Verify the way a human reviewer would, in a real browser, with quantitative checks wherever possible.

When

• After any change touching rendered UI (components, templates, styles, client-side logic)
• Before reporting a UI subtask complete in the orchestrator loop (feeds VERIFY, step 2)
• Skip only for changes with no runtime surface (type-only, test-only, docs)

Protocol

Run every step. A failure at any step means: fix, then rerun from step 1. Never hand back partially verified work.

If the chrome-devtools MCP tools are deferred, load the needed set in ONE ToolSearch call first (new_page, navigate_page, take_screenshot, list_console_messages, list_network_requests, resize_page, lighthouse_audit).