30 lines
958 B
Markdown
30 lines
958 B
Markdown
|
# Sprint 201 Plan: Resource Lock Constraints II (Generation and Queue)
|
||
|
|
|
||
|
|
## Context
|
||
|
|
Schema support must be paired with generation and queue diagnostics.
|
||
|
|
|
||
|
|
## Goals
|
||
|
|
1. Infer locks during taskitem generation
|
||
|
|
2. Surface lock conflicts in queue readiness
|
||
|
|
3. Emit deterministic conflict warnings
|
||
|
|
|
||
|
|
## Steps
|
||
|
|
|
||
|
|
### Step 2044: Lock inference heuristics in generator (10 tests)
|
||
|
|
Infer lock names from requirement/task signals.
|
||
|
|
|
||
|
|
### Step 2045: Queue lock-conflict detection (10 tests)
|
||
|
|
Detect overlapping locks across ready tasks.
|
||
|
|
|
||
|
|
### Step 2046: `resource_conflict_unresolved` warning class (8 tests)
|
||
|
|
Emit deterministic warning packet without hard blocking.
|
||
|
|
|
||
|
|
### Step 2047: Queue lock conflict summary metrics (8 tests)
|
||
|
|
Report conflict counts and affected task IDs.
|
||
|
|
|
||
|
|
### Step 2048: Sprint 201 Integration Summary (8 tests)
|
||
|
|
Add `editor/src/Sprint201IntegrationSummary.h`.
|
||
|
|
|
||
|
|
## Architecture Gate
|
||
|
|
- Queue must expose lock conflicts deterministically for scheduler consumption.
|