Socket snapshot carries the nodes waiting for a machine, so a reconnecting browser restores their queued dots

backend/fluksio/api/routes/flows.py

@@ -907,6 +907,8 @@ def snapshot_payload(
     two have to agree, so they build the message here rather than each their
     own. ``emits`` is what the bus counted while nobody was listening — a
     client that reconnects between two pages would otherwise start from zero.
+    ``queued`` is the nodes waiting for a machine, for the same reason: the bus
+    announces a wait once, and a client that missed it would draw the node idle.
 
     ``only`` bounds it to a set of message names, which is what a wall panel
     gets: the values its own dashboards draw, and none of the rest — no node
@@ -925,6 +927,7 @@ def snapshot_payload(
             "paused": [],
             "logs": [],
             "emits": {},
+            "queued": [],
         }
     return {
         "type": "snapshot",
@@ -934,6 +937,7 @@ def snapshot_payload(
         "paused": controller.paused_flows(),
         "logs": list(event_bus.recent_logs),
         "emits": dict(event_bus.emits),
+        "queued": controller.placer.snapshot()["waiting"] if controller.placer else [],
     }