feat: declare and execute SCUM guided installs

2026-07-27 20:09:14 +08:00
parent 08fa5488f2
commit 2ae27bb746
21 changed files with 185 additions and 9 deletions
@@ -32,3 +32,18 @@ Platform SHALL preserve a deployment value when an update omits it and SHALL cle
 #### Scenario: Optional command is cleared
 - **WHEN** an editor submits `stopCommand` in its explicit clear list
 - **THEN** Platform SHALL store no stop command for the next deployment revision
+
+### Requirement: SCUM guided deployment is template-owned
+For a frozen SCUM guided-install assignment, Run SHALL execute the declared SCUM installation template rather than requiring an operator-provided install or start command. The operator supplies only the protected target root and plugin create inputs.
+
+#### Scenario: Missing runtime prerequisites are installed silently
+- **WHEN** a Windows SCUM guided-install detects a required declared Microsoft runtime is absent
+- **THEN** Run SHALL obtain the approved Microsoft artifact, invoke only its fixed silent installer arguments, verify the runtime marker, and continue only when verification passes
+
+#### Scenario: SteamCMD installs into the selected root
+- **WHEN** a valid SCUM guided-install is executed for root `C:\\scumserver`
+- **THEN** Run SHALL invoke SteamCMD with `+force_install_dir C:\\scumserver`, anonymous login, App `3792580`, validation, and quit as separate argument values
+
+#### Scenario: Guided execution does not disclose raw values remotely
+- **WHEN** Run completes or fails a SCUM guided-install
+- **THEN** its progress, result, evidence, artifact names, and uploaded logs SHALL contain no raw root, command line, credential, or installer URL