windows_vm_guilisted

# windows_vm_gui — drive the supplied Windows GUI Use this for exploratory GUI QA/QC and visual verification that cannot be expressed through `windows_devkit` commands alone. The operator supplies the VM and application state. Observe first, start or open only what is absent, and reset once when all testing is finished. ## Preflight and tool availability The harness adapter declares the managed streamable-HTTP `windows-mcp` server before the harness launches. Claude, Codex, and OpenCode expose it where their active adapter supports Windows MCP. Kimi and Vibe are unsupported until their adapters gain an equivalent injection mechanism. The harness tool list may be fixed at launch. If Windows MCP tools are absent, do not run persistent registration commands or edit user/project harness configuration. Report the adapter state from `./sc vm status --json`. State `unknown` with no `SC_HARNESS` means this session predates the adapter identity contract: relaunch through the engine so it can inject the active harness identity. State `unsupported` means the active adapter declares no injection mechanism; it is an honest capability stop, not a reason to fabricate GUI access or relaunch repeatedly. ## Missing guest Windows-MCP Windows-MCP is baked guest toolchain, never an ad-hoc test dependency. If it is missing, the operator must use the `configure_winbox` flow to: 1. Add Python 3.13+ (for example, `Python.Python.3.13`) to the fork's committed winget manifest and import it in