polish

# Pre-Release Polish Repository state: ```! git rev-parse --abbrev-ref HEAD git status --short git diff --stat 2>/dev/null | tail -1 ``` Base ref argument (optional): $ARGUMENTS ## Rules - Read every changed file fully before reviewing - never assess code you haven't opened - Only flag real issues, not style preferences already handled by the formatter - Do NOT add comments, docstrings, or type annotations to code that doesn't have them - Distinguish legitimate operational logging (`logger.info`, `logger.error`) from debug leftovers (`console.log`, `console.debug`) - When fixing, make minimal targeted edits - don't refactor surrounding code - Only flag issues in changed/added lines, not pre-existing code - Reuse suggestions must point to a specific existing function/utility in the codebase, not hypothetical "you could extract this" - Do not flag efficiency on cold paths, one-time setup code, or scripts that run once ## Phase 1: Automated Checks Run the project's lint + type-check command. Check CLAUDE.md for the correct validation command (commonly `pnpm check`, `just check`, `cargo clippy`, `uv run ruff check`, etc.). If checks fail: 1. Fix all errors 2. Re-run checks until clean 3. Then proceed to Phase 2 If no validation command is found in CLAUDE.md, ask the user what to run. ## Phase 2: Diff Analysis Determine what changed: 1. Check for uncommitted changes: `git diff` + `git diff --cached` 2. Check for untracked (`??`) files in `git status --short`. Include ne...