v0.41.2: fix controller-route auto-connect + dead dashboard cross-drive block

containerOnNetwork misread the absent-key '<nil>' as "already attached", so
wireController skipped docker network connect -> traefik 502'd felhom.<domain>.
Now lists network names and matches exactly. Also removed dashboard.html's dead
CrossDrive* block (slice-8C leftover) that 500'd the dashboard via gt <nil> 0,
exposed once v0.41.1 made the dashboard reachable.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

CHANGELOG.md

@@ -1,5 +1,19 @@
 ## Changelog
 
+### v0.41.2 — fix controller-route auto-connect + dead dashboard cross-drive block (2026-06-11)
+
+Two fixes found while live-validating v0.41.1 routing on guest 9201:
+- **`containerOnNetwork` false-positive (v0.41.1 regression):** the membership check used
+  `{{index .NetworkSettings.Networks "traefik-public"}}`, whose output for an absent key is `<nil>`
+  (non-empty) — so `wireController` thought the controller was already attached and **skipped the
+  `docker network connect`**. traefik then matched the route but 502'd (backend unresolvable). Fixed by
+  listing the network names and matching exactly. Live: `felhom.<domain>` now reaches the controller.
+- **Dead cross-drive dashboard block (pre-existing, slice-8C leftover):** `dashboard.html` still
+  referenced `.CrossDriveTotal/.CrossDriveConfigured/.CrossDriveFailed`, which the de-privileged
+  dashboard handler stopped providing — so `gt <nil> 0` **500'd the entire dashboard**. Only surfaced
+  now because v0.41.1 finally made the dashboard reachable. Removed the dead block (cross-drive backup
+  is the host agent's job since 8C).
+
 ### v0.41.1 — wire the controller dashboard into traefik (`felhom.<domain>` routing) (2026-06-11)
 
 Completes v0.41.0: the base-infra bring-up stood up traefik/cloudflared/filebrowser but nothing routed