review-correctness

# Review Correctness Analyze code for bugs and correctness problems. Return structured findings. ## Step 1: Determine the Scope Determine what to review: - If a specific **diff command** was provided (e.g., `git diff --cached`, `git diff main...HEAD`), use that. - If a **file list or directory** was provided, review those files directly (read the full files, not a diff). - If **neither** was provided, default to diffing against the repository's default branch (detect via `gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'`). ## Step 2: Review 1. For diff scope: run the diff command to obtain the changes. For file scope: read the specified files. 2. For each file, read enough surrounding context to understand the code 3. Apply the bug determination criteria and return findings in the output format below ## Bug Determination Criteria Flag an issue only when ALL of these hold: 1. It meaningfully impacts the accuracy, performance, security, or maintainability of the code 2. The bug is discrete and actionable (not a general codebase issue or combination of multiple issues) 3. Fixing it does not demand rigor beyond what exists in the rest of the codebase 4. In diff mode: the bug was introduced in the changeset (do not flag pre-existing bugs). In file scope mode: this criterion does not apply 5. The author would likely fix the issue if aware of it 6. The bug does not rely on unstated assumptions about the codebase or author's intent 7. Speculation is insuffi...