Flow canvas draws panel I/O ports as panel:<id>:<port> endpoints that open their panel in the Panels dialog

docs/interface/dashboards.md

@@ -437,7 +437,9 @@ message:
 The credential may publish to its `in` messages even when a dashboard is
 locked, and may upload an artifact named after one
 (`PUT /artifacts?name=<message>`), which is how a microphone sends a recording.
-`out` messages are read only.
+`out` messages are read only. The flow canvas draws each port as an endpoint,
+an `in` port feeding the nodes that consume its message and an `out` port fed
+by the nodes that produce it.
 
 !!! note "If the local link is wrong"
 

docs/interface/flow-editor.md

@@ -9,10 +9,11 @@ The graph runs left to right on desktop and top to bottom on phones.
 
 - **Nodes** show their execution status.
 - **Edges** pulse when values pass through. Click one to inspect its payload.
-- **Endpoints** show flow inputs, dashboard widgets and nodes in other flows
-  that exchange messages with this flow. A value passing lights one up in a
-  sweep: left to right when it sends into the flow, right to left when it reads
-  out of it.
+- **Endpoints** show flow inputs, dashboard widgets, panel I/O ports and nodes
+  in other flows that exchange messages with this flow. A value passing lights
+  one up in a sweep: left to right when it sends into the flow, right to left
+  when it reads out of it. Click a panel port to open its panel in the Panels
+  dialog.
 
 Values update over a websocket. A connection banner tells you when the editor
 cannot reach the engine.