adversarial-qalisted

# /adversarial-qa — Exploratory QA Exercise a feature in the running app and surface anything that looks wrong, confusing, or likely to bite a real user. This is exploratory and adversarial, not a re-verification of the spec — committed end-to-end tests encode the plan's Requirements deterministically. Your job is to go beyond them. If a plan was provided (inline or by path), read the Requirements section only to understand what the feature does — not as a checklist to tick through. --- ## What to do 1. Determine the surface(s). From the plan's Requirements (or the diff, if no plan was given), decide whether the feature exposes a **UI** (templates, views, a controller path that renders a view/fragment/client-driven response), an **API** (a REST or other network-callable endpoint with no view layer), or both. Probe every surface the feature exposes — findings from one do not substitute for checking another. 2. Set up and drive the feature, per surface identified in step 1. - **UI surface** — start the local dev server with the project's dev-server command and drive the feature at the documented app URL (both in `AGENTS.md` → *Commands*) in a browser via the Playwright MCP. When you are done, stop it with the documented stop command — never `kill` by PID or hunt processes with `lsof`. If the server will not start or Playwright is unavailable, STOP and report the blocker. Do not substitute `curl`, SQL, or any other workaroun