Virtualization tab: scoping plan — Incus on grid, what is and isn't feasible

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

PLAN.md

@@ -785,16 +785,12 @@ what it has moved.
     filed under "decided, no action", and this is the change that would make closing it
     free.
 
-- **A Virtualization tab** — asked for 2026-09-23, not started, and **large**. Run and
-  manage **LXC containers and virtual machines** from the console, the way Proxmox does —
-  which is the comparison Ham Lab has invited since its first line. Nothing exists yet.
-  What a future session has to settle before writing code: which stack (libvirt/KVM +
-  `virsh` is the obvious one for VMs; LXC or Incus for containers, and Incus covers both);
-  whether it manages what is already installed or installs it; where disk images live
-  (`tank` on `grid`, local NVMe elsewhere); console access (SPICE/VNC proxied through the
-  daemon, or a serial console over the existing terminal machinery, which would reuse
-  `internal/term`); snapshots and clones; and what it does on a host with no virtualisation
-  at all, which is every host here today. Worth scoping as its own plan before starting.
+- **A Virtualization tab** — asked for 2026-09-23; **scoped 2026-10-09 in `VIRTUALIZATION.md`**,
+  not started. Incus 6.0 LTS on `grid` (the only sensible VM host), containers and VMs in one
+  list with console/shell through the terminal machinery, snapshots, exports, and the old
+  Proxmox estate on `tank` as a later import. That file has the host probe, the decisions
+  (NVMe pool, `192.168.200.0/24` bridge because the LAN is a /8, the Docker `FORWARD` fix,
+  ARC cap) and the phased build.
 
 
 ## Open questions