30 lines
990 B
Markdown
30 lines
990 B
Markdown
|
# Sprint 211 Plan: Intent-vs-Closeout Consistency Gate
|
||
|
|
|
||
|
|
## Context
|
||
|
|
Execution closeout can pass while original sprint intent remains partially implemented.
|
||
|
|
|
||
|
|
## Goals
|
||
|
|
1. Add explicit intent-coverage scoring per sprint
|
||
|
|
2. Require intent evidence links per closeout check
|
||
|
|
3. Block closeout when intent coverage is below threshold
|
||
|
|
|
||
|
|
## Steps
|
||
|
|
|
||
|
|
### Step 2094: Intent-to-check traceability model (10 tests)
|
||
|
|
Map sprint goals/steps to concrete implementation and test evidence.
|
||
|
|
|
||
|
|
### Step 2095: Intent coverage scorer (10 tests)
|
||
|
|
Compute per-sprint intent coverage percentage.
|
||
|
|
|
||
|
|
### Step 2096: Closeout consistency gate (8 tests)
|
||
|
|
Fail closeout when coverage threshold is not met.
|
||
|
|
|
||
|
|
### Step 2097: Intent drift diagnostics export (8 tests)
|
||
|
|
Emit unimplemented intent items with evidence gaps.
|
||
|
|
|
||
|
|
### Step 2098: Sprint 211 Integration Summary (8 tests)
|
||
|
|
Add `editor/src/Sprint211IntegrationSummary.h`.
|
||
|
|
|
||
|
|
## Architecture Gate
|
||
|
|
- `EXECUTION-READY` status requires both gate pass and intent coverage threshold pass.
|