Virtual Admin Link development package

Target: windows/arm64
Version: V220
Source commit: 8cec22c5bdd7737c06626edb1262eaf51f712626

Run `VirtualAdminLink.exe version` to verify startup. No installation, service, external runtime, autostart or firewall change is required. This development build is not production E2EE approved; see DEPENDENCIES.md. This architecture currently contains the CLI only. The CLI and MCP remain available through owner-only local IPC. For private human password entry with an agent-owned process pipe, run `VirtualAdminLink.exe gui-connect --relay HOST:PORT --endpoint-type mobile --computer-id ID`. When the agent already knows the password before launch, append `--password-stdin` and send one password line through that waiting process pipe; the human mode never reads a password from stdin. Each successful gui-connect adds one session, returns a target_ref and keeps its own owner-bound pipe for later calls; a second target requires a second invocation. The MCP adapter assigns only agent-approved targets and requires target_ref when one agent has several assigned targets. If the agent runtime cannot re-enter that yielded pipe, use `VirtualAdminLink.exe continue` with the emitted short-lived continuation token as the first stdin line and optional canonical API request JSON lines after it; never put that token in an argument or file. The public connect-via-link guide defines timeout recovery. A directly owned terminal session can use `VirtualAdminLink.exe connect --relay HOST:PORT --endpoint-type mobile --computer-id ID --password-stdin`. Keep that process open, then run `VirtualAdminLink.exe discover`, `VirtualAdminLink.exe call` or `VirtualAdminLink.exe mcp` from sibling processes.
