Merge back from main

.claude/agents/endpoint-group-planner.md

@@ -1,6 +1,6 @@
 ---
 name: endpoint-group-planner
-description: Proactively use this agent to find existing similar endpoint groups that can be used as copy templates for new Umbraco Management API endpoint implementations for testing including builders and helpers. This agent identifies the best existing patterns to replicate.\n\nExamples:\n- <example>\n  Context: User wants to implement tools for a new API endpoint group\n  user: "I need to implement Segment endpoint tools - what similar existing endpoints should I copy from?"\n  assistant: "I'll use the endpoint-group-planner agent to find the most similar existing implementations to use as templates"\n  <commentary>\n  The user needs to find existing patterns to copy from, so use the endpoint-group-planner to identify similar implementations.\n  </commentary>\n</example>\n- <example>\n  Context: User is starting work on a new endpoint group and needs reference implementations\n  user: "What existing endpoint groups are most similar to Webhook management that I can copy from?"\n  assistant: "Let me use the endpoint-group-planner to find the closest existing implementations to use as templates"\n  <commentary>\n  User needs reference implementations to copy from, perfect use case for finding similar patterns.\n  </commentary>\n</example>
+description: Proactively use this agent to find existing similar endpoint groups that can be used as copy templates for new Umbraco Management API endpoint implementations for testing including builders and helpers. This agent identifies the best existing patterns to replicate. It can also be used for incomplete endpoint groups to help plan completion by understanding other similar endpoints in other groups.\n\nExamples:\n- <example>\n  Context: User wants to implement tools for a new API endpoint group\n  user: "I need to implement Segment endpoint tools - what similar existing endpoints should I copy from?"\n  assistant: "I'll use the endpoint-group-planner agent to find the most similar existing implementations to use as templates"\n  <commentary>\n  The user needs to find existing patterns to copy from, so use the endpoint-group-planner to identify similar implementations.\n  </commentary>\n</example>\n- <example>\n  Context: User is starting work on a new endpoint group and needs reference implementations\n  user: "What existing endpoint groups are most similar to Webhook management that I can copy from?"\n  assistant: "Let me use the endpoint-group-planner to find the closest existing implementations to use as templates"\n  <commentary>\n  User needs reference implementations to copy from, perfect use case for finding similar patterns.\n  </commentary>\n</example>\n- <example>\n  Context: User wants to complete missing endpoints in a partially implemented group\n  user: "I need to complete the remaining 3 Media endpoints to reach 100% coverage"\n  assistant: "I'll use the endpoint-group-planner to analyze what's missing and find similar implementations to copy from"\n  <commentary>\n  User needs gap analysis and completion planning for existing group, perfect use case for identifying missing endpoints and finding copy templates.\n  </commentary>\n</example>
 tools: Glob, Grep, Read, Edit, MultiEdit, Write, NotebookEdit, BashOutput, KillBash
 model: sonnet
 color: yellow
@@ -9,7 +9,7 @@ color: yellow
 You are a pattern-matching expert who finds the best existing endpoint group implementations to use as copy templates for new Umbraco Management API endpoints.
 
 **Primary Goal:**
-Find existing similar endpoint groups that can be directly copied and adapted for new implementations.
+Find existing similar endpoint groups that can be directly copied and adapted for new implementations, or analyze gaps in partially implemented groups and plan their completion.
 
 **Core Process:**
 1. **Analyze the Target**: Understand the new endpoint group's characteristics (CRUD operations, hierarchical structure, search capabilities, etc.)

.claude/commands/analyze-coverage.md

@@ -0,0 +1,60 @@
+# /analyze-coverage
+
+Regenerates the Umbraco MCP endpoint coverage analysis report by comparing implemented tools against the full API endpoint list.
+
+## Usage
+```
+/analyze-coverage
+```
+
+## Description
+This command analyzes the current state of MCP tool implementation and generates a comprehensive coverage report showing:
+- Overall coverage statistics
+- Coverage breakdown by API group
+- Missing endpoints for each group
+- Priority recommendations for implementation
+- Quick wins (nearly complete sections)
+
+## Steps Performed
+1. **Regenerate API endpoint list** from the Orval-generated Umbraco client
+   - Parse `src/api/umbraco/client.ts` to extract all API methods
+   - Group endpoints by API category/tag from the OpenAPI spec
+   - Update `docs/analysis/api-endpoints-analysis.md` with the complete endpoint list
+2. Scan all implemented MCP tools in `src/umb-management-api/tools/`
+3. Match implemented tools against API endpoints
+4. Calculate coverage percentages per API group
+5. Generate formatted report with statistics and recommendations
+6. Save report to `docs/analysis/UNSUPPORTED_ENDPOINTS.md`
+
+## Output
+The command updates the `UNSUPPORTED_ENDPOINTS.md` file with:
+- Total endpoint count and coverage percentage
+- Alphabetically organized API groups with coverage status
+- List of missing endpoints for incomplete groups
+- Priority recommendations for implementation
+- Quick wins section highlighting nearly complete groups
+
+## Example Output
+```
+🔍 Analyzing Umbraco MCP endpoint coverage...
+📖 Parsing API endpoints from documentation...
+   Found 37 API groups
+🔧 Scanning implemented MCP tools...
+   Found 269 implementations
+📊 Calculating coverage statistics...
+📝 Generating coverage report...
+✅ Coverage report generated successfully!
+   Output: docs/analysis/UNSUPPORTED_ENDPOINTS.md
+
+📈 Summary:
+   Total Endpoints: 393
+   Implemented: 269
+   Coverage: 68%
+   Missing: 124
+```
+
+## Notes
+- The command uses the `api-endpoints-analysis.md` as the source of truth for available endpoints
+- Coverage is calculated by matching tool implementations against endpoint names
+- The report is organized alphabetically by API group for easy navigation
+- Status indicators: ✅ Complete (100%), ⚠️ Nearly Complete (80%+), ❌ Not Implemented (0%)