ha: fresh HAOS install + VNC console for the HAOS CLI

The backup-restore from the x86 instance left Core stopped with the
Supervisor idle and healthy-looking — no restart, download, or disk
activity, and it survived a guest reboot. The old config was minimal,
so: fresh 18.1 image, configure from scratch (old disk kept aside as
*.old-restored). Add VNC graphics + virtio-gpu while the domain was
down: the HAOS CLI runs only on the graphical console (no serial
getty), so without this there is no way into a broken guest — view it
via Cockpit's Virtual Machines page (cockpit-machines now installed).

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

ha/ha_van.xml

@@ -1,8 +1,12 @@
 <!-- Home Assistant OS VM — aarch64 port for the Pi 4 "wan" host.
      Same identity as wayback's x86 ha_van: MAC 52:54:00:ad:0a:01 is pinned to
      10.42.0.50/"homeassistant" by van-ap-dnsmasq. 2 GiB RAM (Pi has 3.7 total),
-     machine=virt + AAVMF EFI, virtio disk/net. Data migrated via HA full backup
-     (x86 qcow2 can't move across architectures). -->
+     machine=virt + AAVMF EFI, virtio disk/net. Fresh 18.1 install, configured
+     from scratch (a backup-restore from the x86 instance left Core stopped and
+     Supervisor idle; the old config was minimal, so it was abandoned).
+     VNC graphics + virtio-gpu: the HAOS CLI lives on the graphical console
+     (its serial console runs no getty), so this is the only way in without
+     SSH add-ons — view it via Cockpit's Virtual Machines page. -->
 <domain type='kvm'>
   <name>ha_van</name>
   <uuid>af014c94-de20-4f52-8d6b-438f16cd82e6</uuid>
@@ -45,6 +49,10 @@
     <console type='pty'>
       <target type='serial' port='0'/>
     </console>
+    <graphics type='vnc' port='-1' listen='127.0.0.1'/>
+    <video>
+      <model type='virtio'/>
+    </video>
     <rng model='virtio'>
       <backend model='random'>/dev/urandom</backend>
     </rng>