Verified inventory of what this dev qube CAN and CANNOT do against the Windows testbed - Admin API, qube lifecycle, tags, netvm, firewall, loop devices, CI, local tooling - plus the exact environment map (loops, ISOs, pools) and a list of false limitations…
Validate a QWT build's REAL behavior end-to-end on the Windows test guest (win-idd-*) via tools/qtest — unattended, self-healing across reboots, and honest. Use whenever asserting that an installer/agent/driver change actually works: install → reboot →…
Rules for running any experiment against a VM or long-running system - baselines, single-variable changes, waits with real failure modes, and instruments proven before use. Load this before writing any test/probe/e2e script or any wait loop.
What this dev qube (win-idd-mgmt) can do to the testbed through the Qubes Admin API over qrexec — create/remove qubes, set properties, features and tags, import volumes, drive power state — plus the exact calling convention and the traps that make results…
Own BOTH ends of the updates-proxy path by running tinyproxy in this dev qube, instead of guessing about infrastructure you cannot see or asking the user to restart it. Use whenever guest traffic through qubes.UpdatesProxy misbehaves - truncated bodies,…
Determine what a Windows test guest is ACTUALLY doing mid-flight - processes, phase, progress rate - instead of inferring it from silence. Use whenever a long guest operation (DISM/CBS servicing, a large download, a feature update, a benchmark) is running and…