windows-qalisted

Build, install and verify a libi desktop build on the Windows QA VM. Use before shipping anything Windows-facing, or whenever a build must be put in front of a real Windows user. Encodes the traps that have each cost hours — npm ci vs npm install, CI=1, processes dying with the SSH session, what "installed" actually means, and the big one — the VM is an elevated administrator, so an elevated pass proves nothing about a real user.
Nagellabs/libi · ★ 2 · AI & Automation · score 72

Install: claude install-skill Nagellabs/libi

# Windows QA — driving a test build onto the VM Every rule here comes from a failure that happened. Do not relax one without evidence. **Connection details, the VM's name and its firewall rules are NOT in this repo** — they are in `docs-local/release/windows-qa-runbook.md`, which also carries the fuller narrative. Read that first; this file is the rule list. **Start with "The VM is an ADMINISTRATOR" below.** It is the newest rule and the only one that has let a broken build reach users. ## Getting on the box, and putting it away The VM is not left running between sessions, and it is not left *existing* either. The end-of-session move snapshots it and deletes the VM, disk, NIC and public IP, which drops the standing cost from ~$15/month to ~$3. Two consequences that will bite you if you assume otherwise: - **Start with `restore`, not `up`.** `up` builds a fresh box and re-runs an hour of provisioning; `restore` attaches the snapshot and comes back with the installed app, the app's data directory and the build tree exactly as they were left. - **The public IP does not survive.** It is released on the way down and a new one is allocated on the way back. Never hardcode it, in a script or in a doc — resolve it, or use the lab wrapper's own ssh, which looks it up. The runbook named a fixed IP in three places and all three went stale the first time the lab was put away properly. Reaching it is gated on a firewall that allows exactly one source address, so a cha