docker: drop the fleet-wide updates list

A view shows one machine: the one in the switcher. Seeing another machine's
state means switching to it, not a hub-side page that reaches across — and
this was one. Recorded as a decision so it does not get rebuilt.

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

PLAN.md

@@ -18,6 +18,7 @@ stub tab or a roadmap item.
 | Data | `/home/core/apps/hamlab/` — `config.yaml`, `state.db` (SQLite) | `apps/` is the nightly rsync target to `grid`, so it's backed up for free. |
 | Ingress | NPM proxy host `hamlab.bigham.dev` → `:8100`, LE cert, WebSockets on, caching off, force-SSL + HSTS + HTTP/2 set in a **second** API call (NPM drops them on create-with-new-cert) | `*.bigham.dev` already resolves; the proxy host alone makes it live. |
 | Repo | Gitea `mitchell/hamlab`, private, `main` | Created 2026-09-17. |
+| Machines | **A view shows one machine: the one in the switcher.** No hub-side page lists or aggregates what its nodes are doing. To see or change anything on another machine, switch to it. | Mitchell, 2026-09-25, cutting a fleet-wide updates list out of the Docker tab. The switcher is the only place a machine is chosen, so there is exactly one answer to "which machine am I looking at" — a page that quietly reaches across breaks that, and it is never obvious which machine an action would land on. The hub still *proxies* for a node, and hub-only admin (Machines, Users, Settings, Alerts) is unaffected. |
 
 ## Layout
 
@@ -580,8 +581,8 @@ something long in one, switch away and back, refresh — it's all still there.
   keeps its own 4000-entry ring, since `docker events` forgets after about a minute),
   **Shell** (`docker exec`, handed to the Terminal tab) and **Limits** (`docker update` for
   memory, CPU and restart policy); an **updates** tab giving the whole machine at once with
-  a per-container indicator in the list; the same across every machine, asked of the hub;
-  and **schedules**, which write `/etc/cron.d/hamlab-docker` and call
+  a per-container indicator in the list; and **schedules**, which write
+  `/etc/cron.d/hamlab-docker` and call
   `hamlab docker-update <id>` — the shape the ZFS schedules already use.
   Also done: Ham Lab keeps working when `dockhand` is removed. It remembers where a
   container's bind mounts pointed (`mounts` in `state.json`) and resolves a stack through