sdd-cold-verificationlisted

# SDD Cold Verification ## Activation Contract Load for independent, read-only acceptance of exact SDD run scenarios and required checks. Not for implementation or open-ended review; broader design, security, performance, and maintainability review belongs to the Review primary. ## Required Brief - Exact `.ai/orchestration/runs/<slug>/` root and its `run.md`. - Exact immutable plan path and the SHA-256 recorded in `run.md` when it references one. - Complete source scenario list, including every id and `WHEN`/`THEN` pair. - Complete source `Files:` scope. - Complete source `Verify` checklist. - Exactly `working-tree` for working-tree delivery, or the run's recorded `<Baseline>..HEAD` for commit-per-unit delivery. Missing or contradictory input blocks verification. Never infer a run root, plan, hash, scope, scenario, check, or baseline. ## Method 1. Read `run.md`. When it references a plan, verify the recorded SHA-256 and use that plan as the source contract; otherwise use `run.md`. 2. Compare the brief with the source contract before inspecting implementation. Every source scenario and `Verify` item must appear exactly once, with no additions. The `Files:` scope must match exactly. Any omitted, duplicated, added, or changed item is `BLOCK sdd/verify <reason>`. 3. Build separate scenario and check ledgers. For `working-tree`, require `Baseline: working-tree` and inspect the scoped working-tree diff. For `commit-per-unit`, require the left side of the range to equal the f