code-reviewlisted

# Code Review Perform the SDD phase `Validate` for exactly one pull request. Verification means ensuring the implementation satisfies the linked issue, follows repository instructions, preserves outside behavior, has sufficient tests/evidence, and introduces no blocking defects. ## Workflow 1. Resolve the exact repository and PR. Record the current head SHA before reviewing. 2. Read the PR title, body, base/head branches, full commit list, complete diff, changed files in context, all issue comments, reviews, inline comments, review threads, and unresolved conversations. 3. Read every explicitly linked issue and all of its comments. Reconstruct the controlling `Specify`, `Clarify`, `Plan`, and `Tasks`. 4. Read root and applicable nested `AGENTS.md` files, relevant architecture, design, API, domain, security, test, and process documentation. 5. Inspect callers, tests, types, configuration, history, blame, and established patterns needed to evaluate the change. 6. Run relevant local validation when practical. Inspect failed remote checks to determine if they are introduced by the PR, pre-existing, flaky, environmental, or unrelated. 7. Apply the `grilling` investigation discipline before asking anything. 8. Comment only when there is a demonstrated defect, regression, security vulnerability, missing behavior, explicit rule violation, material ambiguity, or to respond to an existing review thread. 9. Every blocking finding must include affected file/line, concrete failure/risk