chore(fleet): sync operator memory, hatch menu dialogs, and watchdog alerts

docs/CHROMEBOX-RUNBOOK.md

@@ -64,7 +64,7 @@ host → veth IP:port (e.g. 10.201.87.2:9420)
 ### chromebox-watchdog (browser health)
 
 - **Script:** `/home/super/Projects/NetVM/bin/chromebox-watchdog.sh`
-- **Timers:** `chromebox-watchdog-<profile>.timer` (one per profile: muse, pip, 646, opm)
+- **Timers:** `chromebox-watchdog-<profile>.timer` (one per profile — every active registry node: muse, pip, 646, opm, def, dev)
 - **Cadence:** every 2 minutes
 - **Log:** `/home/super/Projects/NetVM/chromebox-watchdog.log` (10 MB rotation, 1 backup gen)
 - **Per-profile Chromium output:** `/home/super/Projects/NetVM/chromebox-<profile>.log`
@@ -233,7 +233,7 @@ in the NetVM repo — check `git status` if it's gone.
 **Symptoms:** `pgrep -af netvm-cdp-relay` shows relays on ports like 9269, 9278,
 9353, 10239, 10355 (hash-derived, not registry ports).
 **Cause:** old node-ups or queue tests. Harmless but confusing.
-**Fix:** kill them. Only 9410/9420/9430/9440 should be running.
+**Fix:** kill them. Only the registry ports (9410/9420/9430/9440/9450/9455) should be running.
 
 ## Fleet Status From Blind Shells
 
@@ -246,7 +246,7 @@ falls back to host watchdog evidence (`bin/host_evidence.py`):
   `cdp-relay-watchdog.log` / `chromebox-watchdog.log` (both are
   silent-when-healthy) prove the node is up → `ACTIVE [*]`.
 - `UNKNOWN` means neither live probes nor host evidence could decide
-  (e.g. def/dev have no relay-monitor coverage).
+  (e.g. watchdog timers not installed yet for that node).
 - Host evidence never overrides a live local signal, so a fresh outage
   observed on the host always wins over a minutes-old watchdog run.