docs: update test-case-enhancement.md

Author: wislertt

.amazonq/rules/test-case-enhancement.md

@@ -1,213 +1,78 @@
 # Test Case Enhancement Rules
 
-## Assistant Workflow for Adding Comprehensive Test Cases
+## Simple Enhancement Workflow
 
-### Automated Workflow (Recommended)
+When user requests test case enhancement:
 
-For single problem enhancement:
+### 1. Problem Resolution
 
-1. **Use automation script**: `./.amazonq/rules/test-case-enhancement/scripts/enhance_single_problem.sh <problem_name>`
-2. **Verify results**: `./.amazonq/rules/test-case-enhancement/scripts/verify_enhancement.sh <problem_name>`
+- Use active file context or user-provided problem name
+- If unclear, run: `poetry run python .templates/check_test_cases.py --threshold=10 --max=1`
 
-For batch enhancement:
-
-1. **Find problems**: `./.amazonq/rules/test-case-enhancement/scripts/find_problems_needing_enhancement.sh`
-2. **Batch enhance**: `./.amazonq/rules/test-case-enhancement/scripts/enhance_batch_problems.sh`
-
-### Manual Workflow (Fallback)
-
-When user requests to enhance test cases for a problem, the assistant will:
-
-### 1. Problem Resolution (Priority Order)
-
-- **FIRST**: Try to resolve from context - check active file path or user-provided problem name
-- **SECOND**: If context resolution fails, THEN run `poetry run python .templates/check_test_cases.py --threshold=10 --max=1` to auto-detect 1 problem with <10 test cases
-- **LAST**: If both above fail, ask user to explicitly specify problem name
-
-### 2. Test Case Generation
-
-- Read `leetcode/{problem_name}/README.md` for problem understanding
-- Analyze existing test cases in `leetcode/{problem_name}/tests.py`
-- Generate comprehensive test cases covering:
-    - **Edge cases**: Empty inputs, single elements, boundary values
-    - **Corner cases**: Maximum/minimum constraints, special patterns
-    - **Normal cases**: Typical scenarios with varied complexity
-    - **Error cases**: Invalid inputs (if applicable)
-
-### 3. Initial Validation
-
-- Run `make p-test PROBLEM={problem_name}` to verify current implementation
-- **If errors found**:
-    - DO NOT update implementation automatically
-    - Only update test cases if they're incorrect
-    - If implementation seems wrong, ASK USER first before modifying
-
-### 4. JSON Template Update
-
-- Update corresponding `.templates/leetcode/json/{problem_name}.json`
-- Add new test cases to `test_cases` field in proper format
-- Maintain existing test structure and naming conventions
-
-### 5. Backup and Regeneration Process
-
-- **Backup**: Move `leetcode/{problem_name}/` to `.cache/leetcode/{problem_name}/`
-- **Regenerate**: Run `make p-gen PROBLEM={problem_name} FORCE=1`
-- **Lint check**: Run `make p-lint PROBLEM={problem_name}`
-- **Iterate**: If lint fails, update JSON and regenerate until passes
-
-### 6. Solution Preservation
-
-- Copy `solution.py` from backup to newly generated structure
-- Run `make p-test PROBLEM={problem_name}` to verify tests pass
-- **If tests fail**: Go back to step 4, update JSON, and iterate until passes
-
-### 7. Cleanup and Restore
-
-- **CRITICAL**: Remove entire newly generated `leetcode/{problem_name}/` directory
-- **CRITICAL**: Restore original structure from `.cache/leetcode/{problem_name}/` backup
-- **CRITICAL**: Only THEN copy enhanced `test_solution.py` from generated files to restored structure
-- **CRITICAL**: Preserve existing solution class parametrization - if original test had multiple solution classes, restore them
-- Verify final state with `make p-test PROBLEM={problem_name}`
-- Clean up backup directory after successful verification
-
-## Test Case Quality Standards
-
-### Coverage Requirements
-
-- **Minimum 10 test cases** per problem
-- **Total test cases after enhancement must exceed the threshold** used for detection (e.g., if threshold=10, final count must be >10)
-- **Edge cases**: 20-30% of total test cases
-- **Normal cases**: 50-60% of total test cases
-- **Corner cases**: 20-30% of total test cases
-
-### Test Case Categories
-
-#### Edge Cases
-
-- Empty inputs: `[]`, `""`, `None`
-- Single element: `[1]`, `"a"`
-- Boundary values: `[0]`, `[1]`, `[-1]`
-- Maximum/minimum constraints from problem description
-
-#### Corner Cases
-
-- Duplicate elements: `[1,1,1]`
-- Sorted/reverse sorted arrays: `[1,2,3]`, `[3,2,1]`
-- All same elements: `[5,5,5,5]`
-- Alternating patterns: `[1,0,1,0]`
-
-#### Normal Cases
-
-- Mixed positive/negative numbers
-- Various array sizes within constraints
-- Different data patterns and structures
-- Representative problem scenarios
-
-### JSON Format Requirements
-
-- Use single quotes for Python strings in test cases
-- Follow existing parametrize format
-- Maintain type hints in parametrize_typed
-- Ensure test_cases string is valid Python list syntax
-- **NEVER include custom solution classes** in test_imports - only import the main solution class specified in solution_class_name
-- **PRESERVE existing solution class parametrization** - if original test had multiple solution classes, restore them after JSON regeneration
-
-## Automation Scripts 🤖
-
-**RECOMMENDED APPROACH**: Use prebuilt scripts in `.amazonq/rules/test-case-enhancement/scripts/` to streamline the enhancement process:
-
-### Find Problems Needing Enhancement
+### 2. Enhancement Process
 
 ```bash
-# Find problems with ≤10 test cases (default)
-./.amazonq/rules/test-case-enhancement/scripts/find_problems_needing_enhancement.sh
-
-# Custom threshold and max results
-./.amazonq/rules/test-case-enhancement/scripts/find_problems_needing_enhancement.sh 8 15
+# Simple 4-step process:
+# 1. Update JSON template with more test cases (12-15 total)
+# 2. Backup original
+mv leetcode/{problem_name} .cache/leetcode/{problem_name}
+# 3. Regenerate with enhanced tests
+make p-gen PROBLEM={problem_name} FORCE=1 && make p-lint PROBLEM={problem_name}
+# 4. Restore original solution, keep enhanced tests
+cp .cache/leetcode/{problem_name}/solution.py leetcode/{problem_name}/solution.py
 ```
 
-### Enhance Single Problem
+### 3. Verification
+
+- Run `make p-test PROBLEM={problem_name}`
+- Fix any incorrect expected values in test cases
+- Update JSON template with corrections
+
+### 4. Restore Backup
 
 ```bash
-# Enhance specific problem (handles full workflow automatically)
-./.amazonq/rules/test-case-enhancement/scripts/enhance_single_problem.sh <problem_name>
+# Copy enhanced test_solution.py to backup
+cp leetcode/{problem_name}/test_solution.py .cache/leetcode/{problem_name}/
+# Restore all original files (preserves user edits)
+rm -rf leetcode/{problem_name}
+mv .cache/leetcode/{problem_name} leetcode/{problem_name}
 ```
 
-### Batch Enhancement
+## Test Case Standards
 
-```bash
-# Enhance up to 10 problems with ≤10 test cases (default)
-./.amazonq/rules/test-case-enhancement/scripts/enhance_batch_problems.sh
+### Coverage Requirements
 
-# Custom batch size and threshold
-./.amazonq/rules/test-case-enhancement/scripts/enhance_batch_problems.sh 5 8
-```
+- **Minimum 12 test cases** per problem
+- **Edge cases**: Empty inputs, single elements, boundary values
+- **Corner cases**: Maximum/minimum constraints, duplicates, sorted arrays
+- **Normal cases**: Mixed scenarios with varied complexity
 
-### Verify Enhancement Results
+### JSON Format
 
-```bash
-# Verify enhancement was successful
-./.amazonq/rules/test-case-enhancement/scripts/verify_enhancement.sh <problem_name>
-```
+- Use single quotes for Python strings: `'hello'` not `"hello"`
+- Follow existing parametrize format
+- Ensure valid Python list syntax in test_cases field
 
-## Manual Commands Reference
+## Quick Commands
 
 ```bash
-# Find problems needing more test cases
-poetry run python .templates/check_test_cases.py --threshold=10 --max=1
+# Find problems needing enhancement
+poetry run python .templates/check_test_cases.py --threshold=10
 
 # Test specific problem
 make p-test PROBLEM={problem_name}
 
 # Generate from JSON template
 make p-gen PROBLEM={problem_name} FORCE=1
 
-# Lint specific problem
+# Lint check
 make p-lint PROBLEM={problem_name}
 ```
 
-## Error Handling
-
-- **Implementation errors**: Ask user before modifying solution code
-- **Test failures**: Update JSON template and regenerate
-- **Lint failures**: Fix JSON format and iterate
-- **Backup failures**: Ensure `.cache/leetcode/` directory exists
-
 ## Success Criteria
 
 - All tests pass with enhanced test cases
-- Total test cases exceed the threshold used for detection
-- Minimum 10 comprehensive test cases per problem
-- Original solution code preserved and working
+- Minimum 12 comprehensive test cases per problem
+- Original solution code preserved
+- **Enhanced test cases in final test_solution.py**
 - JSON template updated for future regeneration
-- Clean final state with no temporary files
-
-## Automation Benefits
-
-Using the prebuilt scripts provides several advantages:
-
-### ⚡ **Speed & Efficiency**
-
-- **Single command execution** - No need to remember complex multi-step workflows
-- **Batch processing** - Enhance multiple problems simultaneously
-- **Automatic cleanup** - No manual file management required
-
-### 🛡️ **Safety & Reliability**
-
-- **Automatic backups** - Original code always preserved
-- **Error handling** - Graceful failure recovery
-- **Validation checks** - Syntax and structure verification
-
-### 📊 **Visibility & Tracking**
-
-- **Progress reporting** - Real-time status updates
-- **Result verification** - Automatic test case counting
-- **Success metrics** - Clear pass/fail indicators
-
-### 🔄 **Consistency**
-
-- **Standardized process** - Same workflow every time
-- **Quality assurance** - Built-in lint and validation checks
-- **Reproducible results** - Eliminates human error
-
-**Recommendation**: Always use automation scripts for test case enhancement unless debugging specific issues requires manual intervention.