A live socket stays with the machine it was opened for

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-21 23:53:18 -07:00
parent 3c7e46104c
commit 5412e316de
3 changed files with 18 additions and 2 deletions
@@ -580,6 +580,15 @@ against what it holds, a request against the page that should have made it.
 5. ✅ **"Everything is up to date." sat in a 20px sliver of a card**, flush to its border, where
   the package list it shares the card with is meant to be.

+6. ✅ **A terminal of the hub's was asked for on a node.** Found in Firefox against the live
+   console, which says out loud what Chromium swallows: `wss://…/api/nodes/grid/terminals/
+   adfdeecb/attach`, where `adfdeecb` was one of the hub's — `grid` had no terminals at all. A
+   pane builds its address when it connects, from whichever machine the console is pointed at
+   *now*; switch machine while one is reconnecting and the reconnect goes to the new one. The
+   address is fixed when the pane opens. The same was true of a service's log socket, and is
+   fixed with it. Verified by walking the console around the fleet with a terminal open and
+   checking every socket against the machine that actually owns what it asked for.
+
 ## Checked and fine

 Machine titles on every page and against an offline or never-reached machine; the colour a