windows_testinglisted

# windows_testing — use the disposable Windows test guest The controller exposes one guest, `W10C-Testing`, with the same commands from Halo and Dev. It cannot select another domain or run commands/read files on Halo. Cash/Jed own installation, guest credentials, the immutable recovery snapshot, and live provisioning. ## Initialize once per checkout On Halo: ```bash sc vm test init local ``` On Dev, use the operator-supplied SSH alias whose key is restricted to the controller ForceCommand: ```bash sc vm test init ssh halo-windows-test ``` Initialization changes only the transport. Every later verb is identical. If the controller or guest is unconfigured, surface the structured error; do not change SSH, libvirt, networking, credentials, or snapshots to repair it. ## Run one test session ```bash sc vm test status sc vm test acquire --owner "<shell/task>" sc vm test start sc vm test push <local-file> artifacts/test.zip sc vm test exec --cwd run --command-file <local-script.ps1> sc vm test pull results/result.json <local-result> sc vm test reset working sc vm test release ``` `acquire` saves an owner-only opaque lease locally; later commands use it without putting it in argv or logs. Keep the lease for the whole push/exec/pull and reset sequence. A competing mutation fails rather than joining the active session. Report the test result and reset/release result separately. If `acquire` cannot save the token it hands the lease straight back and reports `lease_not_saved` w