30 lines
958 B
Markdown
30 lines
958 B
Markdown
|
# Sprint 202 Plan: Resource Lock Constraints III (Validation and Scheduler Contract)
|
||
|
|
|
||
|
|
## Context
|
||
|
|
Lock handling needs validation and scheduler-facing contract output.
|
||
|
|
|
||
|
|
## Goals
|
||
|
|
1. Add lock-name and scope validation checks
|
||
|
|
2. Emit scheduler lock contract packet
|
||
|
|
3. Add ambiguity diagnostics for lock scope
|
||
|
|
|
||
|
|
## Steps
|
||
|
|
|
||
|
|
### Step 2049: Validation lock name-format checks (10 tests)
|
||
|
|
Validate lock naming conventions and invalid forms.
|
||
|
|
|
||
|
|
### Step 2050: Scope ambiguity diagnostics (10 tests)
|
||
|
|
Flag ambiguous local/global lock usage.
|
||
|
|
|
||
|
|
### Step 2051: Scheduler lock contract emitter (8 tests)
|
||
|
|
Emit deterministic lock contract payload for scheduler adapters.
|
||
|
|
|
||
|
|
### Step 2052: Lock validation aggregate report fields (8 tests)
|
||
|
|
Expose lock-quality metrics in validation summaries.
|
||
|
|
|
||
|
|
### Step 2053: Sprint 202 Integration Summary (8 tests)
|
||
|
|
Add `editor/src/Sprint202IntegrationSummary.h`.
|
||
|
|
|
||
|
|
## Architecture Gate
|
||
|
|
- Scheduler-facing lock semantics must be explicit and validated.
|