fix: Resolve false positive coverage reporting for untested functionality
Major improvements to coverage analysis accuracy:
**Fixed Coverage Calculation Logic:**
- Remove false positive where untested issues showed 100% coverage
- Require actual keyword overlap for coverage validation
- Treat requirements with no extractable keywords as gaps (not covered)
- Changed from assuming coverage if any tests exist to requiring keyword matches
**Enhanced Requirement Extraction:**
- Add patterns for data operations (read, store, save, load, retrieve, fetch)
- Add data handling patterns (file, database, storage, content)
- Add format handling patterns (schema, json, markdown, ast)
- Intelligent analysis of simple issues with enhanced requirement generation
- Title-based requirement extraction for comprehensive coverage
**Stricter Coverage Validation:**
- Requirements without keywords always considered gaps
- No more false positives for completely untested functionality
- Improved gap detection for better accuracy
**Results:**
- Issue #3 now correctly shows 33.3% coverage (was 100% false positive)
- Issue #11 still correctly shows 100% coverage (comprehensive tests)
- More detailed requirement breakdown for simple issues
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
tegwick
e0b4ab0124