docs: Update EXECUTION_CHECKLIST.md with Phase 15 completion

- Document 7 extraction async jobs tools added
- Document 2 A2A pipelines implemented (regression-watch, post-incident-cleanup)
- Update MCP server total to 135 tools across 18 namespaces
- Add implementation notes and fixes applied
This commit is contained in:
saravanakumardb1 2026-03-05 22:07:53 -08:00
parent 40db19a389
commit ccf71b898c

View File

@ -332,6 +332,42 @@ MCP server total after this commit: **114 tools** across 17 namespaces.
MCP server total after this commit: **126 tools** across 17 namespaces. MCP server total after this commit: **126 tools** across 17 namespaces.
## 21) Phase 15 — Highest-ROI next steps: 7 extraction async jobs tools + 2 A2A pipelines ✅ COMPLETE
### Extraction async jobs tools (7 added)
| Tool | Description |
| -------------------------------------- | ------------------------------------------- |
| `extraction.extractBatch` | Batch extraction with shared configuration |
| `extraction.submitJob` | Async job submission with webhook callbacks |
| `extraction.getJob` | Get job status/results by ID |
| `extraction.listJobs` | List recent async jobs |
| `extraction.getProductRateLimitStatus` | Per-product or summary rate limits |
| `extraction.resetProductRateLimit` | Admin rate limit reset |
| `extraction.sidecarMonitoringState` | Detailed sidecar circuit breaker state |
All tools map to existing extraction-service endpoints and require admin role.
### A2A pipelines (2 added)
| Pipeline | Tool | Description |
| --------------------- | ------------------------- | --------------------------------------------------------- |
| Regression Watch | `a2a.regressionWatch` | Monitor error clusters → auto-create diagnostics sessions |
| Post-Incident Cleanup | `a2a.postIncidentCleanup` | Resolve clusters + delete policies + export audit logs |
Both pipelines support `dryRun` mode and use existing platform-service endpoints.
### Implementation notes
- Added 7 client functions to `extraction-client.ts`
- Fixed TypeScript optional parameter error in `extractionGetProductRateLimitStatus`
- Created pipeline files with proper Zod schemas and error handling
- Fixed platform-client function names (`telemetryClusters` not `telemetryListClusters`)
- Used correct `TelemetryCluster` interface properties (`id` not `clusterId`)
- Both pipelines registered in `server.ts` via `a2a-tools.ts`
MCP server total after this commit: **135 tools** across 18 namespaces.
## 11) Phase 5+ quick sanity checks ## 11) Phase 5+ quick sanity checks
- If you make telemetry policy-aware clients: - If you make telemetry policy-aware clients: