find-bugs

Review changes on this branch for bugs, security vulnerabilities, and code quality issues. For each changed file, identify and list: For each potential issue: Before finalizing, you MUST: Prioritize : security vulnerabilities > bugs > code quality Skip : stylistic/formatting issues For each issue: If you find nothing significant, say so - don't invent issues. Do not make changes - just report findings. I'll decide what to address. - Get the FULL diff: git diff $(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')...HEAD - If output is truncated, read each changed file individually until you have seen every changed line - List all files modified in this branch before proceeding - All user inputs (request params, headers, body, URL components) - All database queries - All authentication/authorization checks - All session/state operations - All external calls - All cryptographic operations - Check if it's already handled elsewhere in the changed code - Search for existing tests covering the scenario - Read surrounding context to verify the issue is real - List every file you reviewed and confirm you read it completely - List every checklist item and note whether you found issues or confirmed it's clean - List any areas you could NOT fully verify and why - Only then provide your final findings - File:Line - Brief description - Severity : Critical/High/Medium/Low -...