## 1. Contract and domain model

- [x] 1.1 Add typed SCUM deployment templates, config mappings, discovery markers, verification checks, and safe deployment projections to `platform/domain`.
- [x] 1.2 Extend Run assignment/result DTOs and conversion with versioned deployment plans and bounded evidence; keep public projections redacted.
- [x] 1.3 Add validator rules and capability gating for `deployment.scum.v1`, bounded evidence, operation-specific requirements, and required verification checks.

## 2. Platform lifecycle behavior

- [x] 2.1 Freeze the selected SCUM template into install/adopt jobs and distinguish `install` from `adopt` dispatch semantics.
- [x] 2.2 Persist Run evidence into the safe server deployment projection and gate ready/running state on required verification.
- [x] 2.3 Add server deployment status DTO/API projection for preflight, scan, mapping, verification, and stable failure codes.

## 3. SCUM plugin assets

- [x] 3.1 Extend the manifest schema and domain conversion for `serverDeployments`.
- [x] 3.2 Declare the SCUM Windows SteamCMD template, executable/config markers, field mappings, adoption scan markers, and post-install checks in the first-party manifest.
- [x] 3.3 Add manifest validation and fixture tests for the SCUM template and unsafe-value rejection.

## 4. Verification and handoff

- [x] 4.1 Add Platform unit/contract tests covering install/adopt semantics, target/capability rejection, mapping validation, evidence projection, and redaction.
- [x] 4.2 Add protocol documentation and Run coordination notes for the independent executor implementation.
- [x] 4.3 Run Go tests, plugin typecheck/test/manifest validation, `scripts/check-structure.sh`, and `openspec validate complete-scum-deployment-lifecycle --strict`.