Flow inputs carry an origin hint, run or panel

The Inputs editor and the canvas label show it, and the run forms leave
panel inputs out.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WgBfkm4rCmtd1T4vHWjEPx

docs/concepts/flows.md

@@ -96,13 +96,18 @@ Declare messages supplied by dashboard controls, the API or run parameters as
 the flow's **Inputs**. Give live inputs a starting value:
 
 ```json
-{"inputs": [{"spec": {"name": "setpoint", "dtype": "float"}, "initial": 21.0}]}
+{"inputs": [{"spec": {"name": "setpoint", "dtype": "float"}, "initial": 21.0, "origin": "panel"}]}
 ```
 
 This seeds `house.setpoint` in flow `house` if it has no value yet. Later
 publications replace it. Batch inputs are run parameters, and batch outputs
 select the run's result. See [Where a node's values come from](values.md).
 
+`origin` says what writes an input: `run` (the default) for a parameter a run
+passes in, `panel` for a dashboard or panel control. The canvas labels each
+input with it, and the run form leaves panel inputs out, so a run keeps their
+starting value. The engine treats both the same.
+
 ## Drafts and publishing
 
 - **Saving** stores a draft; the engine keeps running the published version.

docs/concepts/values.md

@@ -47,8 +47,10 @@ The initial value seeds an unset live message. Later publications take over;
 changing the starting value does not overwrite a value already in state.
 Use **Publish this value now** in the input row to send it immediately.
 
-The canvas draws flow inputs as labelled endpoints. Without a producer or
-declared input, a consuming node reports `unconnected_input`.
+The canvas draws flow inputs as labelled endpoints, marked `run` or `panel`
+by what writes them. A panel input is one a dashboard or panel control writes,
+and the run form does not ask for it. Without a producer or declared input, a
+consuming node reports `unconnected_input`.
 
 A batch flow's inputs are run parameters. Its **Result** section selects the
 messages returned when the run finishes. See [Runs](runs.md).

docs/interface/flow-editor.md

@@ -80,7 +80,7 @@ Open **Flow settings** from the pencil button in the dock.
 |---|---|
 | **Running** | starts or stops the published live flow's subscriptions, schedules and webhooks |
 | **Mode** | chooses continuous `live` operation or requested `batch` runs |
-| **Inputs** | declares external messages and starting values; batch inputs become run parameters |
+| **Inputs** | declares external messages, their starting values and whether a run or a panel writes them; run inputs become run parameters |
 | **Result** | selects batch output messages |
 | **Contents** | shows the node count and message namespace |