# Investigate a browser regression — acceptance checklist

Record evidence for every checked item. Unchecked or untested is not a pass. This checklist does not execute an integration or authorise external actions.

## Required inputs

- [ ] A local or authorised staging URL.

- [ ] Reproduction steps, expected behaviour and the suspected revision.

## Output checks

- [ ] The URL, application revision, browser version and viewport are recorded.

- [ ] The original steps reproduce the symptom before the fix.

- [ ] One operator owns the browser session and traces are checked for private data.

- [ ] The original failure and a nearby unaffected behaviour are rerun after the change.

## Deliverables

- [ ] Minimal reproduction

- [ ] Browser evidence bundle

- [ ] Source-linked hypothesis

- [ ] Before/after regression receipt

## Evidence and decision

Evidence links: [fill in]
Untested paths: [fill in]
Unresolved findings: [fill in]
Reviewer: [fill in]
Decision and scope: [fill in]

## Boundaries

- Choose a host for each stage and verify its tool mapping. Pass evidence explicitly between stages; the listed resources do not automatically configure or invoke one another.

- The supplied agent’s tool aliases may require adaptation to your host and installed browser server.

- Do not let parallel workers drive the same browser session. Browser traces can contain private page content; inspect them before sharing.

Workflow: https://undominated.ai/workflows/#debug-a-browser-regression