Revert "Add test coverage analysis tools with multi-format support (#4)"

This reverts commit 70c51c2.

Author: willibrandon

README.md

@@ -25,11 +25,6 @@ NetContextServer empowers AI coding assistants like Cursor AI to deeply understa
   - 🔍 **Deep Dependency Visualization**: See transitive dependencies with interactive, color-coded graphs
   - 🧩 **Smart Grouping**: Visually group related packages for easier navigation
   - 📊 **Update Recommendations**: Identify outdated packages and security issues
-- 📊 **Test Coverage Analysis**: Deep insights into your test coverage
-  - 🎯 **Multi-Format Support**: Parse coverage data from Coverlet, LCOV, and Cobertura XML
-  - 📈 **Detailed Reports**: File-level coverage percentages and uncovered line tracking
-  - 🔄 **Branch Coverage**: Track method-level branch coverage where available
-  - 💡 **Smart Recommendations**: Get suggestions for improving test coverage
 - ⚡ **Fast & Efficient**: Quick indexing and response times for large codebases
 
 ## 🚀 Quick Start
@@ -83,10 +78,6 @@ Now Cursor AI can understand your codebase! Try asking it questions like:
 - "What's the current base directory for file operations?"
 - "Help me think through the authentication system design"
 - "Document my reasoning about this architectural decision"
-- "Analyze test coverage for MyService.cs"
-- "Show me uncovered lines in the authentication module"
-- "What's the overall test coverage percentage?"
-- "Which files have the lowest test coverage?"
 
 ## 📚 Documentation
 
@@ -104,11 +95,6 @@ Now Cursor AI can understand your codebase! Try asking it questions like:
 - 📖 **File Content Access**: Read source files with safety checks and size limits
 - 🛡️ **Security**: Built-in safeguards for sensitive files and directory access
 - 🎯 **Pattern Management**: Flexible ignore patterns for controlling file access
-- 📊 **Coverage Analysis**: Parse and analyze test coverage data
-  - 📈 **Coverage Reports**: Support for Coverlet JSON, LCOV, and Cobertura XML formats
-  - 🎯 **Line Coverage**: Track which lines are covered by tests
-  - 🌳 **Branch Coverage**: Monitor method-level branch coverage
-  - 💡 **Recommendations**: Get actionable suggestions to improve coverage
 - 💭 **Structured Thinking**: Document and validate reasoning about complex operations
   - 🧩 **AI-Optimized Reasoning**: Based on [Anthropic's research](https://www.anthropic.com/engineering/claude-think-tool) on improving LLM problem-solving
   - 📋 **Task Planning**: Break down complex problems into manageable steps
@@ -201,34 +187,6 @@ Project: MyProject.csproj
           └─ Microsoft.Extensions.DependencyInjection.Abstractions
 ```
 
-6. **Analyze Test Coverage**:
-```bash
-# Set your base directory first
-dotnet run --project src/NetContextClient/NetContextClient.csproj -- set-base-dir --directory "path/to/your/project"
-
-# Analyze coverage from a Coverlet JSON report
-dotnet run --project src/NetContextClient/NetContextClient.csproj -- coverage-analysis --report-path "TestResults/coverage.json"
-
-# Get a coverage summary
-dotnet run --project src/NetContextClient/NetContextClient.csproj -- coverage-summary --report-path "TestResults/coverage.json"
-```
-
-Example coverage analysis output:
-```json
-[
-  {
-    "filePath": "src/MyProject/Services/UserService.cs",
-    "coveragePercentage": 85.3,
-    "uncoveredLines": [42, 43, 88],
-    "branchCoverage": {
-      "ValidateUser()": 75.0,
-      "GetUserById()": 100.0
-    },
-    "recommendation": "Consider adding tests for the user validation error paths"
-  }
-]
-```
-
 ### Search Commands
 
 1. **Text Search**:

docs/getting-started.md

@@ -122,57 +122,6 @@ dotnet run --project src/NetContextClient/NetContextClient.csproj -- add-ignore-
 dotnet run --project src/NetContextClient/NetContextClient.csproj -- get-ignore-patterns
 ```
 
-## Using Coverage Analysis
-
-NetContextServer includes powerful test coverage analysis capabilities that help you understand and improve your test coverage. Here's how to get started:
-
-### 1. Generate Coverage Reports
-
-First, you'll need to generate a coverage report. NetContextServer supports multiple formats:
-
-**Using Coverlet (recommended):**
-```bash
-dotnet test --collect:"XPlat Code Coverage"
-```
-This will generate a coverage report in the `TestResults` directory.
-
-**Using LCOV:**
-If you're using LCOV, make sure your test runner is configured to output LCOV format (`.info` files).
-
-**Using Cobertura:**
-For Cobertura XML format, configure your test runner to output `.cobertura.xml` files.
-
-### 2. Analyze Coverage
-
-Once you have a coverage report, you can analyze it using NetContextServer:
-
-```bash
-# Analyze coverage for detailed per-file information
-dotnet run --project src/NetContextClient/NetContextClient.csproj -- coverage-analysis --report-path "TestResults/coverage.json"
-
-# Get a summary of overall coverage
-dotnet run --project src/NetContextClient/NetContextClient.csproj -- coverage-summary --report-path "TestResults/coverage.json"
-```
-
-### 3. Interpret Results
-
-The coverage analysis provides several key insights:
-
-- **Coverage Percentage**: The percentage of lines covered by tests
-- **Uncovered Lines**: Specific line numbers that aren't covered by tests
-- **Branch Coverage**: For methods with conditional logic, shows how many branches are covered
-- **Recommendations**: Suggestions for improving coverage in specific areas
-
-### 4. Improve Coverage
-
-Use the analysis results to:
-1. Identify files with low coverage
-2. Focus on uncovered lines in critical code paths
-3. Add tests for uncovered branches in complex methods
-4. Track coverage trends over time
-
-For more details on coverage analysis commands and options, see the [Tool Reference](tool-reference.md#coverage-analysis-tools).
-
 ## Troubleshooting
 
 ### Common Issues

docs/tool-reference.md

@@ -422,59 +422,4 @@ The server provides clear error messages for common scenarios:
 - Invalid patterns
 - File size limits exceeded
 - Restricted file types
-- Missing environment variables for semantic search
-
-## Coverage Analysis Tools
-
-### `coverage-analysis`
-
-Analyzes test coverage data from various formats and provides detailed insights.
-
-```bash
-dotnet run --project src/NetContextClient/NetContextClient.csproj -- coverage-analysis --report-path <path> [--format <format>]
-```
-
-**Parameters:**
-- `--report-path`: Path to the coverage report file
-- `--format` (optional): Coverage report format. Supported values:
-  - `coverlet-json` (default): Coverlet JSON format
-  - `lcov`: LCOV format
-  - `cobertura`: Cobertura XML format
-
-**Output:**
-Returns a list of coverage reports for each file, including:
-- File path
-- Coverage percentage
-- List of uncovered lines
-- Branch coverage data (where available)
-- Recommendations for improving coverage
-
-**Example:**
-```bash
-dotnet run --project src/NetContextClient/NetContextClient.csproj -- coverage-analysis --report-path "TestResults/coverage.json"
-```
-
-### `coverage-summary`
-
-Generates a summary of test coverage across all files.
-
-```bash
-dotnet run --project src/NetContextClient/NetContextClient.csproj -- coverage-summary --report-path <path> [--format <format>]
-```
-
-**Parameters:**
-- `--report-path`: Path to the coverage report file
-- `--format` (optional): Coverage report format (same as coverage-analysis)
-
-**Output:**
-Returns a summary object containing:
-- Total number of files
-- Overall coverage percentage
-- Total number of uncovered lines
-- List of files with coverage below threshold
-- List of files with lowest coverage
-
-**Example:**
-```bash
-dotnet run --project src/NetContextClient/NetContextClient.csproj -- coverage-summary --report-path "TestResults/coverage.json"
-``` 
+- Missing environment variables for semantic search