code-reviewlisted

# Code review Review the behavior first, then the shape. ## Pass Check requirement compliance, correctness, regressions, security and privacy risks, test coverage, API compatibility, and unnecessary complexity. Use file and line references when reporting issues. ## Evidence Ground findings in code paths, observable behavior, or missing checks. Separate definite bugs from questions and assumptions. ## Output Lead with actionable findings ordered by severity. Keep summaries secondary, and say clearly when you found no issues.