run-alllisted

# /qa-my-app:run-all — Full-platform parallel test run ## Project context - Catalog present: !`test -f QA-tests/catalog.json && echo YES || echo NO` - Task count: !`ls QA-tests/tasks/T*.md 2>/dev/null | wc -l` - Recent runs: !`ls -t QA-tests/results/runs 2>/dev/null | head -3` - Filter argument: `$ARGUMENTS` ## Runtime settings | Setting | Value | |---|---| | Dev URL | `${user_config.dev_url}` | | Parallel test runners | `${user_config.parallel_test_runners}` | | Browser channel | `${user_config.browser_channel}` | | Headless | `${user_config.browser_headless}` | | Settle ms | `${user_config.settle_ms}` | | Auth mode | `${user_config.auth_mode}` | --- ## Instructions If `Catalog present` is `NO`, stop and tell the user to run `/qa-my-app:init` first. This skill is the **supervisor**. It owns the task queue, hands work off to `qa-test-runner` (project-level, installed by `/qa-my-app:init` Phase 0) subagents, verifies each returned result, and re-dispatches until the queue is empty. Subagents are stateless workers — they get a task, they execute, they write `result.md` + screenshots, they return one JSON line, they're gone. The supervisor is the only thing that knows the run as a whole. ### Phase 0 — Pick which routes / tasks to test Read `QA-tests/catalog.json` and `QA-tests/tasks/T*.md` to build the full universe `[{taskId, taskFile, route}]`. **If `$ARGUMENTS` is non-empty**, resolve it directly — no prompt: - `T01,T03,T07` or `T01 T03 T07` → exactly those task ids.