version: "1.0.0" name: qa description: Run browser flows and snapshot checks, then score release readiness. allowed-tools:

• Read
• Bash

/qa

Use this mode when the agent should validate a product surface, not just inspect code.

Objective

Run repeatable browser verification, collect evidence, and turn it into a ship/no-ship QA report.

Workflow

1. Choose the target URL and named browser session.
2. Import --session-bundle <path> first when the target requires authenticated state.
3. Use --mode diff-aware plus --base-ref when the goal is to probe the pages changed by the current diff from a preview base URL.
4. Run one or more checked-in flows when behavior needs end-to-end validation.
5. Add --a11y when accessibility regressions matter, and scope it with --a11y-scope plus --a11y-impact when needed.
6. Add --perf with --perf-budget and --perf-wait-ms when user-perceived performance needs to be enforced.
7. Capture or compare a snapshot when visual/text drift matters.
8. Score the result with categorized findings, severity, evidence, and a recommendation.
9. Load .codex-stack/baseline-decisions/ so known regressions can be downgraded, suppressed, or flagged for refresh explicitly.
10. Save the QA report under .codex-stack/qa/, including annotated screenshot evidence when snapshot failures occur.
11. Refresh .codex-stack/qa/trends.json and .codex-stack/qa/trends.md so the operator can compare the latest run against prior QA history.
12. Publish tracked copies into docs/qa/ when the shipping workflow needs GitHub-linkable evidence.
13. Render docs/qa/ through scripts/render-qa-pages.ts when the operator needs a static review site.

CLI

bun src/cli.ts qa http://127.0.0.1:4173/dashboard --flow release-dashboard --snapshot release-dashboard --session demo --json
bun src/cli.ts qa http://127.0.0.1:4173/dashboard --flow release-dashboard --snapshot release-dashboard --a11y --a11y-scope main --perf --perf-budget lcp=2s --perf-budget cls=0.1 --session demo --json
bun src/cli.ts qa http://127.0.0.1:4173/login --flow release-full-demo --snapshot release-login --session demo
bun src/cli.ts qa https://preview.example.com/dashboard --flow release-dashboard --session preview-auth --session-bundle .codex-stack/private/preview-auth.json --json
bun src/cli.ts qa https://preview.example.com --mode diff-aware --base-ref origin/main --session preview --json
bun scripts/qa-run.ts --fixture ./tmp/qa-fixture.json --json
bun scripts/qa-trends.ts --dir .codex-stack/qa --json

Output format

• Overall QA status
• Health score
• Findings with category + severity
• Diff-aware route probe summary
• Snapshot evidence
• Accessibility and performance summaries plus artifact paths
• Regression triage summary plus applied, expired, and unresolved decisions
• Flow pass/fail summary
• Recommendation
• Trend delta vs previous runs via .codex-stack/qa/trends.json

Guardrails

• Do not claim QA passed without runtime evidence.
• Prefer checked-in flows and named snapshots for repeatable environments.
• Use --session-bundle instead of embedding secrets into flows when preview or staging authentication is required.
• Use --mode diff-aware only when the provided URL is the deploy base, not a single leaf page.
• Refresh a snapshot baseline only when the UI change is intentional.