30 lines
970 B
Markdown
30 lines
970 B
Markdown
# Sprint 200 Plan: Resource Lock Constraints I (Schema)
|
|
|
|
## Context
|
|
Concurrency/resource mutual exclusion is not modeled in taskitems.
|
|
|
|
## Goals
|
|
1. Add `resourceLocks` to taskitem schema
|
|
2. Add lock scope rules (node-local vs global)
|
|
3. Preserve backward compatibility for existing taskitems
|
|
|
|
## Steps
|
|
|
|
### Step 2039: `resourceLocks` schema extension (10 tests)
|
|
Add optional lock list to annotated taskitem contracts.
|
|
|
|
### Step 2040: Lock scope parser and validator (10 tests)
|
|
Parse and validate default-local + `global:` prefixes.
|
|
|
|
### Step 2041: Backward-compatibility serialization path (8 tests)
|
|
Ensure older taskitems remain valid without locks.
|
|
|
|
### Step 2042: Lock metadata documentation packet (8 tests)
|
|
Emit deterministic schema metadata for clients.
|
|
|
|
### Step 2043: Sprint 200 Integration Summary (8 tests)
|
|
Add `editor/src/Sprint200IntegrationSummary.h`.
|
|
|
|
## Architecture Gate
|
|
- Taskitem schema must model mutual exclusion without breaking existing contracts.
|