test: achieve 80%+ test coverage on 8 core modules

.claude/CLAUDE.md

@@ -1,26 +1,31 @@
 # .claude Directory Rules
 
 ## Context Engineering Principles
+
 - WRITE: Use plans/ for persistent task tracking
-- SELECT: Load context/ files based on task requirements  
+- SELECT: Load context/ files based on task requirements
 - COMPRESS: Keep context window <80% utilization
 - ISOLATE: Respect directory boundaries
 
 ## Directory Navigation
+
 - Always check for nested CLAUDE.md when entering subdirectories
 - Subdirectory rules override parent rules
 - Load relevant context before ANY operation
 
 ## Directory Structure
+
 - **context/**: Domain-specific knowledge and patterns
 - **plans/**: Task planning and tracking with state management
 - **commands/**: Reusable command patterns and workflows
 - **findings/**: Research reports and investigation results (YYYYMMDD_ prefix)
 - **settings.local.json**: MCP server configuration
 
 ## Usage
+
 When working in this directory:
+
 1. Check for local CLAUDE.md files in subdirectories
 2. Load appropriate context based on task type
 3. Use plans/ for structured task management
-4. Reference commands/ for common workflows
+4. Reference commands/ for common workflows

.claude/commands/CLAUDE.md

@@ -11,24 +11,29 @@ Claude Code automatically recognizes any Markdown file in your project's `.claud
 ## Command Types
 
 ### Project Commands (This Directory)
+
 - **prp/**: Product Requirements Prompt commands for feature blueprints
 - **quality/**: Quality check commands for validation and testing
 - **deploy/**: Deployment commands (future)
 
 Commands in this directory are:
+
 - Available to all team members when checked into git
 - Shown as `/project:command-name` in Claude Code
 - Listed with "(project)" suffix in `/help`
 
 ### Personal Commands
+
 You can also create personal commands in `~/.claude/commands/` that are:
+
 - Available across all your Claude Code sessions
 - Private to your local environment
 - Shown as `/personal:command-name`
 
 ## Command Structure
 
 Each command file should include:
+
 1. **Purpose**: Clear description of what the command accomplishes
 2. **Prerequisites**: Required setup, environment, or conditions
 3. **Command Sequence**: Step-by-step instructions or prompts
@@ -38,22 +43,29 @@ Each command file should include:
 ## Advanced Features
 
 ### Parameter Support
+
 Use `$ARGUMENTS` to pass parameters to commands:
+
 ```markdown
 # Example: .claude/commands/analyze-issue.md
 Please analyze and fix the GitHub issue: $ARGUMENTS
 ```
+
 Usage: `/project:analyze-issue 1234`
 
 ### File References
+
 Include file contents using the `@` prefix:
+
 ```markdown
 Review the implementation in @src/utils/helpers.py
 Compare @src/old-version.py with @src/new-version.py
 ```
 
 ### Bash Command Execution
+
 Execute bash commands before the slash command runs using the `!` prefix:
+
 ```markdown
 !git status
 Analyze the current git status and suggest next steps.
@@ -62,6 +74,7 @@ Analyze the current git status and suggest next steps.
 ## Namespacing
 
 Commands are organized by namespace:
+
 - `/project:command-name` - Project-specific commands (this directory)
 - `/personal:command-name` - Personal commands from ~/.claude/commands/
 - `/command-name` - Built-in Claude Code commands
@@ -96,6 +109,7 @@ Include specific line numbers and code examples in your feedback.
 ## Integration with EOL RAG Framework
 
 Our custom commands extend Claude Code for RAG development:
+
 - **PRP commands**: Generate comprehensive implementation blueprints
 - **Quality commands**: Validate Python code and RAG performance
 - **Context-aware**: Leverage .claude/context/ knowledge base
@@ -116,4 +130,4 @@ Our custom commands extend Claude Code for RAG development:
 
 ---
 
-*This directory follows Claude Code's official slash command conventions, enabling powerful custom workflows for the EOL RAG Framework development.*
+*This directory follows Claude Code's official slash command conventions, enabling powerful custom workflows for the EOL RAG Framework development.*

.claude/commands/prepare-pr.md

@@ -1,9 +1,11 @@
 # Prepare Pull Request Command
 
 ## Purpose
+
 Create and push a pull request with proper preparation and description.
 
 ## Prerequisites
+
 - All quality checks passed (run check-quality.md first)
 - Working on feature branch (not main)
 - Changes committed locally
@@ -12,6 +14,7 @@ Create and push a pull request with proper preparation and description.
 ## Command Sequence
 
 ### 1. Ensure Branch is Up to Date
+
 ```bash
 # Fetch latest changes
 git fetch origin main
@@ -26,13 +29,15 @@ git rebase origin/main
 ```
 
 ### 2. Run Final Quality Check
+
 ```bash
 # Quick quality validation
 python -m black src/ tests/ --check && \
 python -m pytest tests/ -q
 ```
 
 ### 3. Review Changes
+
 ```bash
 # View all changes
 git diff origin/main...HEAD
@@ -45,6 +50,7 @@ git log --oneline origin/main..HEAD
 ```
 
 ### 4. Push Branch
+
 ```bash
 # Push to remote
 git push -u origin $(git branch --show-current)
@@ -54,6 +60,7 @@ git push -u origin $(git branch --show-current)
 ```
 
 ### 5. Create Pull Request
+
 ```bash
 # Create PR with title and body
 gh pr create \
@@ -90,6 +97,7 @@ EOF
 ```
 
 ### 6. Alternative: Create Draft PR
+
 ```bash
 # Create as draft for work in progress
 gh pr create --draft \
@@ -99,6 +107,7 @@ gh pr create --draft \
 ```
 
 ### 7. View PR Status
+
 ```bash
 # Check PR checks status
 gh pr checks
@@ -108,6 +117,7 @@ gh pr view --web
 ```
 
 ## PR Title Conventions
+
 - `feat:` New feature
 - `fix:` Bug fix
 - `docs:` Documentation only
@@ -117,6 +127,7 @@ gh pr view --web
 - `chore:` Maintenance
 
 ## Success Criteria
+
 - ✅ Branch up to date with main
 - ✅ All tests passing locally
 - ✅ PR created successfully
@@ -126,6 +137,7 @@ gh pr view --web
 ## Troubleshooting
 
 ### Merge Conflicts
+
 ```bash
 # If rebase has conflicts
 git status
@@ -135,12 +147,14 @@ git rebase --continue
 ```
 
 ### Push Rejected
+
 ```bash
 # If push rejected after rebase
 git push --force-with-lease
 ```
 
 ### PR Checks Failing
+
 ```bash
 # View check details
 gh pr checks
@@ -151,6 +165,7 @@ gh run view <run-id>
 ```
 
 ### Update Existing PR
+
 ```bash
 # Add commits and push
 git add .
@@ -162,8 +177,9 @@ gh pr edit --body "Updated description..."
 ```
 
 ## Best Practices
+
 1. Keep PRs small and focused
 2. Write descriptive commit messages
 3. Respond to review feedback promptly
 4. Update PR description as needed
-5. Link related issues with "Fixes #123"
+5. Link related issues with "Fixes #123"

.claude/commands/prp/CLAUDE.md

@@ -3,13 +3,15 @@
 Systematic planning methodology for creating comprehensive implementation blueprints for any software feature development using context engineering principles.
 
 ## Overview
+
 PRP commands implement the Product Requirements Prompt methodology - a context engineering approach that provides AI coding assistants with comprehensive implementation blueprints for production-ready software development.
 
 **Core Principle**: PRP = PRD + Curated Codebase Intelligence + Agent Runbook
 
 **Key Philosophy**: Context Engineering is the systematic process of giving AI coding assistants a comprehensive mission briefing - complete with requirements, code examples, technical constraints and best practices - before writing code.
 
 ## PRP Context Engineering Workflow
+
 1. **Analyze** - Extract patterns, dependencies, and technical context from codebase
 2. **Create** - Generate comprehensive implementation blueprint with curated intelligence
 3. **Review** - Validate plan accuracy and completeness against current patterns
@@ -31,23 +33,27 @@ PRP commands implement the Product Requirements Prompt methodology - a context e
 PRP commands implement the structured planning methodology documented in [`.claude/context/planning-methodology.md`](../../context/planning-methodology.md).
 
 ### Context Engineering Implementation
+
 PRP commands generate comprehensive implementation blueprints following context engineering principles:
+
 - **System Context**: Global project rules and conventions from `.claude/CLAUDE.md`
 - **Domain Context**: Technology-specific patterns from `.claude/context/`
 - **Task Context**: Feature requirements with technical constraints
 - **Implementation Blueprint**: Phase-based tasks with validation gates (see [Phase Structure](../../context/planning-methodology.md#phase-based-development))
 - **Validation Framework**: Quality gates, testing, and success metrics (see [Defining Success](../../context/planning-methodology.md#success-metrics))
 
 ### Systematic Execution
+
 - Phase-based implementation ([Phase Guidelines](../../context/planning-methodology.md#phase-guidelines))
 - Real-time task tracking with checkbox format
 - Git branch strategy ([Branch Lifecycle](../../context/planning-methodology.md#git-branch-strategy))
 - Quality gates at each phase boundary
 - Performance validation against defined metrics
 
 ## Best Practices
+
 1. Always analyze before creating PRPs
 2. Use systematic task tracking
 3. Validate at each phase
 4. Document lessons learned
-5. Update context with discoveries
+5. Update context with discoveries