Files
gstack/qa/sections/browser-verify.md
T
garrytan 26dc71d586 fix(skills): resolve judge-cited ambiguities in /qa and /plan-eng-review
- tasks JSONL keeps the raw branch as GIT_BRANCH instead of overwriting
  gstack-slug's sanitized BRANCH used for artifact names
- the Codex outside-voice block runs for ready or unverified, matching
  its routing rule
- plan-eng startup names the preamble's own setup prompts; the
  cross-project question waits for Step 0
- /qa 8c: a fix that applies but leaves the finding reproducing gets one
  revised fix, else it is reverted; browser verification names its before
  screenshot; the exploratory loop drops its duplicate 3-step summary
2026-10-06 00:19:36 +00:00

1.1 KiB

Browser repair verification

Use this section only for a browser defect. Re-run the original interaction and an adjacent happy path. The Phase 5 evidence is the before (issue-NNN-result.jpg for an interactive defect, the annotated issue-NNN.png for a static one); capture the after now.

Use the Phase 3 read/flow script in qa-patterns with flow = true for interaction bugs; set its actions and waits to the original reproduction. For static defects use flow = false. Keep the error hook, snapshot, console output and GSTACK_STEP_OK check. Run each flow in one script from the affected URL; tabs do not survive the script.

Use fresh screenshot names, with issue-NNN-after.jpg for the result (add a suffix if it exists). Copy them from the printed ASIDE_DIR to $REPORT_DIR/screenshots/, then Read the copied screenshot. Compare the snapshot tree, DIFF and CONSOLE_ERRORS= with the before evidence.

On fallback, apply browser-setup's $B mapping to the same checks. Functional repairs never load this section.