QA Run

!IMPORTANT: Verification is browser-only. Confirm a scenario by what a user observes in the browser / admin UI / email sandbox — never mark a step passed because a DB query, GraphQL response, or log line says so. If a step can only be confirmed via terminal/DB/GraphQL, that's a plan-defect: log it, don't fake the pass.

Root-causing is not verification. Once a step fails or behaves oddly, a dev runner is encouraged to read the source to explain why and cite file:line in the Finding (see Step 2.3). That's an asset, not a violation of the constraint above — the constraint governs how you confirm a pass, not how you explain a failure.

Step 0: Locate the plan

The argument may be a local path, a Linear issue key, or a Linear URL. Classify it before resolving: