browser-qa

Verification is runtime observation: what you capture from the running app is the evidence; tests and typechecks are CI's output, not yours.

Steps

1. Establish what's under test

Whatever the user said is the scope (a commit SHA, branch name, tag, main, HEAD~5). If they didn't specify one, ask for it.

2. Identify the spec source

Look for the originating spec, in this order:

1. Issue references in the commit messages (#123, Closes #45, GitLab !67), fetched via the workflow in docs/agents/issue-tracker.md.
2. A path the user passed as an argument.
3. A spec file under docs/, specs/, or .scratch/ matching the branch name or feature.
4. If nothing is found, ask the user where the spec is.

3. Drive