browser-testing

# Browser testing ## Contract | Field | Bound contract | |---|---| | Trigger | Browser UI implementation, debugging, or runtime verification; or a PR number, branch name, or `current` to test pages affected by a diff. | | Authority | Read-only. Drives an attached browser to inspect runtime state. No source, VCS, credential, paid, published, deployed, or remote mutation. Fixes are requested from the user, never applied. | | Side effect | Drives an attached browser or a selected browser driver against the local dev server. Writes only local evidence artifacts (screenshots, console logs, test reports). | | Done | Interactive: the changed runtime surface is exercised with clean console/network and correct visual, accessibility, or performance evidence. Diff-scoped: the summary reports every affected route as Pass, Fail, or Skip with reasons, or reports the preflight blocker and what would clear it. | ## Inputs ### Interactive mode - A browser-rendered change to verify or debug (required): the localhost or dev-server URL of the affected page and a description of the surface that changed. - Chrome DevTools MCP attached (required): an MCP server providing screenshot, DOM inspection, console logs, network monitor, performance trace, element computed-styles, accessibility tree, and page-context JavaScript execution tools. - The symptom or verification target (required for debugging, optional for verification): what is wrong, or what must be confirmed. - Logged-in browser state (o...