30 lines
988 B
Markdown
30 lines
988 B
Markdown
|
# Sprint 196 Plan: Long-Range Edit Reliability I (Contracts)
|
||
|
|
|
||
|
|
## Context
|
||
|
|
Long-range multi-file edits need explicit deterministic contracts.
|
||
|
|
|
||
|
|
## Goals
|
||
|
|
1. Define long-range edit contract schema
|
||
|
|
2. Require file-set and dependency closure metadata
|
||
|
|
3. Add blocker classes for incomplete long-range specs
|
||
|
|
|
||
|
|
## Steps
|
||
|
|
|
||
|
|
### Step 2019: Long-range edit contract schema (10 tests)
|
||
|
|
Add schema fields for multi-file edit intent, scope, and constraints.
|
||
|
|
|
||
|
|
### Step 2020: Dependency closure metadata extraction (10 tests)
|
||
|
|
Compute required file/symbol closure for planned edits.
|
||
|
|
|
||
|
|
### Step 2021: Contract completeness validator (8 tests)
|
||
|
|
Reject long-range tasks missing closure-critical fields.
|
||
|
|
|
||
|
|
### Step 2022: Long-range blocker taxonomy (8 tests)
|
||
|
|
Add deterministic blockers for under-specified long-range edits.
|
||
|
|
|
||
|
|
### Step 2023: Sprint 196 Integration Summary (8 tests)
|
||
|
|
Add `editor/src/Sprint196IntegrationSummary.h`.
|
||
|
|
|
||
|
|
## Architecture Gate
|
||
|
|
- Long-range edit tasks must be rejected unless contract-complete.
|