browser-evidence

name	browser-evidence
description	Use when claiming a visible, responsive, interactive, scroll-led, canvas, WebGL, or animated browser result is complete and fresh evidence is needed.

Browser Evidence

Match proof to the claim. A build, HTTP 200, or one hero screenshot does not prove mobile behavior, interaction, motion, or visual quality.

For ordinary visible work, inspect the running page and a key desktop state. Add mobile, primary flow, and serious console/page errors for responsive or interactive work. Add representative states, a short clip or multi-state frames, and fallback review for motion-led work.

Use the bundled scripts when executable browser proof is appropriate. Report pass, partial, or blocked exactly; a missing runtime or unsupported capability is not a successful result.

Read ../../references/evidence-and-handoff.md and ../../references/tooling.md. Use ../../templates/evidence-report.md for a reviewable result.