tcgflow-web-testlisted

# `/tcgflow-web-test` — verify it in a real browser ## When to use The user typed `/tcgflow-web-test …` or said *"web test ES-1234"*, *"check this in the browser"*, *"click through it on UAT"*, *"does my uncommitted change actually work?"*. Use it when the thing to prove is **visual or interaction-level** — the kind of acceptance criterion a green unit suite says nothing about. Not for static review (`/tcgflow-review`), not for the scripted suites (`/tcgflow-test`), and not to be run inside a headless Cockpit run. ## Reading the invocation Everything after the command name is free-form context. Pull out whatever is there; nothing is mandatory. | Fragment | Example | Meaning | |---|---|---| | Task ID | `ES-7030` | The task whose acceptance criteria are the oracle | | Environment keyword | `on uat`, `locally`, `staging` | Resolve to a URL via `config.yaml` → `web_test.environments`, or ask | | URL | `https://app.example-uat.internal/` | Wins over the keyword — use it verbatim | | Auth note | *"I've already logged in using microsoft"* | Reuse the existing browser session; do **not** attempt to sign in | | Focus | *"just the approval dialog"* | Narrows the surfaces to visit | **With no task ID**, the scope is the **uncommitted diff** (`git status` / `git diff`) — the *"does what I just changed actually work?"* case. If that diff clearly belongs to a task in `tasks/active/`, name the task and confirm with the user before pulling in its acceptance criteria or writing anythin