qa-verifylisted

# QA verify (local stack) Verify on the local stack; produce proofs. **Kind** procedure · **Used by** [qa](../../agents/qa.md) · **When** every lane has cleared review and its tests (develop-flow step 6), or before any fix exists on a bug ticket ([reproduction pass](#reproduce), step 2b); the stack boot starts earlier, in parallel with step 3 · **Ends with** a QA report file — or a reproduction report — a proof per user-visible requirement on disk, and a verdict Never edit product code. Put test-data scripts in scratchpad. Use profile stack commands only. <a id="from-pr"></a> ## 0a. Starting from a PR link — outside the flow Inside develop-flow the branch, the worktree and the plan already exist; step 0 pre-warms and step 1 points the stack at them. Invoked on its own with a **PR link or number**, build that context first: ```bash gh pr view <N> --json title,body,headRefName,baseRefName,files,url git fetch <remote> && git worktree add <path> <remote>/<headRefName> ``` Worktree path, base ref and cleanup follow [worktree](../worktree/SKILL.md#naming) — the same naming contract, so nothing collides with a lane the flow owns. Then assemble what steps 1 – 5 read: | Normally from | With only a PR | | --- | --- | | the branch in the dev work log | the PR's head branch, checked out above | | requirements in `$TROIKA_SCRATCHPAD/plans/<TICKET>.md` | that plan if the ticket key in the branch or PR title has one; otherwise the ticket's own surfaces ([ticket surfaces](../plan-r