code-reviewlisted

# Code Review Review the exact change against two independent questions: whether it is built correctly and whether it builds the requested thing. Read `references/evidence.md` when calibrating scope, finding usefulness, or severity. If delegation is explicitly authorized, apply `delegate-work` and assign only distinct review axes such as correctness, security, external compatibility, or rendered interface quality; keep synthesis and deduplication in the main task. ## Respect the Review Contract - Treat a review-only request as read-only. Do not modify code, resolve findings, or change repository state. - When the user explicitly requests review and fixes, complete the evidence-based review first, then correct supported findings and verify the result. - Review only the requested diff and directly affected behavior. Do not turn the review into a general codebase audit. - Preserve the distinction between repository standards and product requirements. ## Pin the Review Scope Resolve and verify the fixed point before reviewing: - the merge base, branch, commit, tag, or working-tree state; - committed, staged, unstaged, and untracked changes in scope; - generated, vendored, lock, schema, and migration files affected by the change. Fail clearly on an invalid base or empty diff. Do not silently substitute a different comparison. Read the full relevant diff and enough surrounding code to understand runtime behavior. Trace changed interfaces to important callers, consumers, te