Feat/qa-visual-evidence: QA lane must screencap and screen-record results

[michaelnaughton-euc]

The QA lane's "screenshot evidence" line was loose enough that a run with no browser door could substitute a static code read and still report done. This makes visual evidence the deliverable: screenshot every changed screen, screen-record the primary flow when the harness can, and post both on the PR — and it gives runners without a first-party browser tool a sanctioned door (headed Playwright bootstrapped outside the checkout) so the mandate is satisfiable.

Prompted by a real blocked run where the runner had no browser tool and the walk silently degraded to a diff read.

flowchart TD
  qa[QA lane dispatched] --> door{Browser door?}
  door -->|first-party tool| walk[Walk the flow]
  door -->|Playwright in checkout| walk
  door -->|none| boot[Bootstrap headed Playwright outside checkout]
  boot --> walk
  door -->|bootstrap impossible| blocked[Report blocked: list what was not captured]
  walk --> caps[Screenshot each changed screen]
  walk --> rec[Screen-record primary flow]
  caps --> post[Post evidence as PR/issue comment]
  rec --> post
  post --> report[Report back to Tech lead]

Loading

🤖 Generated with Claude Code