New Tests for Recent Work

Review recent changes and add missing test coverage where it matters.

Instructions

Step 1: Identify Recent Changes

Run git diff HEAD~1 (or git diff main...HEAD if on a branch) to find what changed. If no git changes, ask the user which files to cover.

Focus on:

• New functions, methods, or components
• Changed behavior in existing code
• New API endpoints or routes
• Modified business logic

Step 2: Audit Existing Coverage