test-fixing

Systematically identify and fix all failing tests using smart grouping strategies. Run make test to identify all failing tests. Analyze output for: Group similar failures by: Prioritize groups by: For each group (starting with highest impact): Identify root cause Implement fix Verify fix Move to next group Infrastructure first: Then API changes: Finally, logic issues: After all groups fixed: User: "The tests are failing after my refactor" - Explicitly asks to fix tests ("fix these tests", "make tests pass") - Reports test failures ("tests are failing", "test suite is broken") - Completes implementation and wants tests passing - Mentions CI/CD failures due to tests - Total number of failures - Error types and patterns - Affected modules/files - Error type : ImportError, AttributeError, AssertionError, etc. - Module/file : Same file causing multiple test failure - Root cause : Missing dependencies, API changes, refactoring impacts - Number of affected tests (highest impact first) - Dependency order (fix infrastructure before functionality) - Identify root cause - Read relevant code - Check recent changes with git diff - Understand the error pattern - Implement fix - Use Edit tool for code changes - Follow project conventions (see CLAUDE.md) - Make minimal, focused changes - Verify fix - Run subset of tests for this group - Use pytest markers or file patterns: uv run pytest...