testing-cyclelisted

______________________________________________________________________ ## testing-cycle Processing feedback: **$ARGUMENTS** ## Phase 1: Classify Feedback Analyze the feedback and assign a classification: | Type | Indicators | Effort | | --------------- | ---------------------------------------------------- | ------- | | Bug (Critical) | Functionality broken, crash, data loss, core feature | High | | Bug (Minor) | UI glitch, cosmetic, edge case, non-blocking | Low | | Gap | Missing feature, expected capability not implemented | Backlog | | Test Correction | Automated test tests wrong behavior, false positive | Medium | | Enhancement | UX improvement, better wording, nice-to-have | Varies | **Present the classification to the user for confirmation before proceeding.** Show: - **Feedback**: (original, quoted) - **Classification**: \[type\] - **Rationale**: (why this classification) - **Proposed action**: (what will be done) Wait for user confirmation. They may reclassify. ## Phase 2: Act by Type ### Bug (Critical) 1. **Investigate**: Find relevant code, understand the root cause - Search for related files using the feedback keywords - Read the relevant source files - Check if there's an existing test covering this behavior 1. **Test first**: - If a test exists but tests the wrong thing → fix the test first (it should now fail) - If no test exists → writ