41 lines
1.4 KiB
Markdown
41 lines
1.4 KiB
Markdown
# Sprint 140 Plan: Program-Wide MCP Wiring Closure and Release Gate
|
|
|
|
## Context
|
|
|
|
With tool-surface, runtime, routing, telemetry, and compatibility controls in
|
|
place, Sprint 140 establishes a single release gate certifying MCP wiring
|
|
closure across the program.
|
|
|
|
---
|
|
|
|
## Goals
|
|
|
|
1. Compose all MCP wiring checks into one deterministic closure gate
|
|
2. Produce release-ready wiring certification packets
|
|
3. Block release on unresolved wiring/runtime/contract drift
|
|
4. Provide low-context, machine-readable remediation guidance
|
|
|
|
---
|
|
|
|
## Steps
|
|
|
|
### Step 1639: MCP closure gate aggregate schema (10 tests)
|
|
### Step 1640: Multi-check gate orchestrator model (10 tests)
|
|
### Step 1641: Wiring closure severity classifier (10 tests)
|
|
### Step 1642: Deterministic remediation planner model (10 tests)
|
|
### Step 1643: `whetstone_run_mcp_closure_gate` MCP tool (8 tests)
|
|
### Step 1644: `whetstone_get_mcp_closure_status` MCP tool (8 tests)
|
|
### Step 1645: `whetstone_get_mcp_remediation_plan` MCP tool (8 tests)
|
|
### Step 1646: Release certification packet model (8 tests)
|
|
### Step 1647: MCP closure publication bundle (8 tests)
|
|
### Step 1648: Sprint 140 integration summary + full-program regression (8 tests)
|
|
|
|
---
|
|
|
|
## Architecture Gate
|
|
|
|
- Closure gate must be deterministic and reproducible
|
|
- Any blocking issue must include explicit structured remediation
|
|
- Certification packets must include provenance and checksums
|
|
- Max 600 lines per header
|