Add fluksio status, and ask for a run's parameters at a terminal

Two halves of the same gap: the CLI could start work but not show you any.

`fluksio status` draws the home screen's top half in a terminal — health and
what is wrong with it, every flow with its state and node count, and the
recent runs and failures under them. `--watch` keeps it there. Rich does the
drawing; it was already installed under fastapi's own CLI, and is named now
because a command depends on it.

`fluksio run` with no parameters at a terminal asks for them, one line per
declared input with its declared value in brackets — so Enter through the lot
is what running the defaults looks like, and an artifact input takes the
`@run:` spelling the engine now resolves. A scripted run is untouched: passing
any parameter, or piping the command, skips the questions, as does --defaults.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019V5bsYGNxcgPs4xXmTPx69

docs/code/cli.md

@@ -12,8 +12,8 @@ should only *run nodes* for an engine elsewhere. It has none of the engine in
 it. See [Remote workers](workers.md).
 
 The command is two things at once: `serve`, `enroll` and `worker` *are* an
-installation, while `login`, `sync`, `run`, `runs` and `sweep` talk to one that
-may be anywhere.
+installation, while `login`, `sync`, `run`, `runs`, `sweep` and `status` talk to
+one that may be anywhere.
 
 ## Where an installation lives
 
@@ -196,6 +196,19 @@ whole reference as JSON still works and is what a script that already holds one
 does — which is the same thing `flow.submit(dataset=run.result["dataset"])`
 does from Python.
 
+Run a flow with no parameters at a terminal and it asks for them, one line per
+declared input, with the declared value in brackets:
+
+```text
+lr (float) [0.05]: 0.01
+epochs (int) [10]:
+dataset (artifact): @run:1758042000123-9f2ab41c.dataset
+```
+
+Enter keeps what is in brackets, so pressing it through the lot runs the
+defaults. Nothing changes for a scripted run: passing any parameter, or piping
+the command, skips the questions, and `--defaults` skips them explicitly.
+
 `--no-sync` runs what is already on the engine. Worth it in a tight loop where
 you know nothing changed, since syncing retires the workers and the next call
 pays its imports again. A directory that declares no flows syncs nothing and
@@ -214,6 +227,20 @@ worker pool and module reconcile, against the ~15 ms of submitting to an
 engine that is already up: `--local` is for "I just want to run it", not for a
 loop you are iterating in.
 
+### `fluksio status`
+
+```sh
+fluksio status [--watch]
+```
+
+The home screen's top half in a terminal: whether the engine is healthy and
+what is wrong if not, then every flow with its state, its node count and
+whether it has unpublished changes, and the last few failures under them.
+
+`--watch` keeps it on screen and refreshes every five seconds until Ctrl-C —
+the cadence the dashboard polls at, since nothing here moves faster. It needs a
+terminal; without one, run it without `--watch` and the output pipes cleanly.
+
 ### `fluksio runs`
 
 ```sh