browser-evidence

• IS: start the app, look at it, capture evidence, stop. One throwaway headless browser per invocation, one derived port per checkout, one evidence folder a verifier can cite per criterion.
• IS NOT: a browser-automation framework, an e2e test suite, an interactive session in the user's real Chrome, a reason to add a dependency to the repo under test, or a pass/fail gate. It produces evidence; the verifier judges it.

Opt-in only. Most tickets are copy, label, and refactor diffs with no browser surface, so this is never a default pipeline step. In captain it belongs in .skills or CAPTAIN_SKILLS for the repos that want it, never in DEFAULT_SKILLS.

Contents

• Workflow checklist
• Phase 1: Decide whether there is anything to look at
• Phase 2: Pick ports and start the app
• Phase 3: Capture with a throwaway browser
• Phase 4: Write the evidence
• Phase 5: Tear down and verify teardown
• Hard rules
• Gotchas
• Related skills