feat: Code review skills + GitHub issue tracking for all findings

[negativeeddy]

Summary

Converts all open code review findings into tracked GitHub issues and adds two VS Code skills for ongoing code review management.

What Changed

New GitHub Labels (5):

• code-review — all code review findings
• priority: critical — must-fix: correctness/data-loss risk
• priority: medium — correctness/maintainability
• priority: low — polish/consistency
• needs-investigation — requires deeper review before fix

New GitHub Issues (24, #78–#101):
All 22 Todo findings from docs/code-review/ plus 2 deep-review items, each labeled with code-review, the appropriate priority, and needs-investigation where applicable.

Priority	Count	Issues
🟡 Medium	8	#78–#81, #82–#85
🟢 Low	16	#86–#101
🔍 Needs Investigation	7	#82–#88

New Skills (2):

1. /code-review — Runs a structured code review sweep and creates labeled GitHub issues for each finding. Supports scoped reviews (full codebase, single project, recent changes).
2. /code-review-fix — Picks up open code-review issues from the board and implements fixes in priority order. Supports argument-based targeting (3, critical, #82, etc.).

Updated Documentation:

• docs/code-review/README.md — Added GitHub issue mapping table and workflow guide

How to Use

# Periodic review sweep (creates new issues)
/code-review

# Work through backlog (fixes 3 highest-priority issues)
/code-review-fix 3

# Fix all critical issues
/code-review-fix critical

# Fix a specific issue
/code-review-fix #82

Files Changed

• .github/skills/code-review/SKILL.md — New skill
• .github/skills/code-review-fix/SKILL.md — New skill
• docs/code-review/README.md — Updated with issue mapping
• scripts/create-code-review-issues.sh — Script for reproducibility