Read .agents/skills/qa/SKILL.md and .agents/qa/config.json, then run project-qa run --root <repo>. If absent, use setup. --filter <id-substring> limits a follow-up run. --base-url <url> selects a temporary website target without editing project settings. Check report.json for the effective baseUrl and tested revision, then confirm the browser destination; API and auth URLs remain separately configured.
Use deterministic scripts. Interactive investigation can repair a failed journey, then put repeatable steps in its tracked suite. Never replace failed live behavior with mocked success.
Reports distinguish pass, fail and blocked, record Git revision, and keep screenshots private. Exit 0 means selected cases passed, 1 means failure, 2 means blocked. Report omitted cases and configured gaps separately. A passing journey proves its assertions, not uninspected visual quality or runtime health. For a UI audit, use the installed ui-regression skill when available and report functional, rendered-quality and runtime verdicts separately.
Read sessions before recovering login, telemetry before production traffic, and surface requirements for relevant components. Runner API defines executable cases and optional browser-network-cli diagnostics, including installation when needed.
Verify cleanup of created data and tabs. Keep saved sessions for the next run. Do not close personal browser tabs, log out providers after each test, or run suites sharing a stateGroup concurrently.