Style the engine's own logs, notice enrolment while serving, say more in status

Four things from a testing pass.

`fluksio serve` printed its own lines through the root logger, which has no
handler and falls back to `INFO:fluksio.cloud.connector:...` — beside uvicorn's
aligned output it reads like something went wrong. The engine's loggers and
alembic's now use uvicorn's own handler. Named rather than configuring the
root: httpx logs every portal call at INFO and none of that is printed today.

`fluksio enroll` writes its config from another process, so an engine already
serving never learned it had been paired. It now looks for one every few
seconds and dials when it appears. `load()` rather than `exists()`, or a file
that does not parse would be restarted forever.

`fluksio status` says where the installation stands with its portal — never
paired, linked, or paired and unreachable, which is the one worth acting on.

`--seed` and `--timeout` had no help text at all. Both say what they are for
now, and the docs say what a seed is actually for: recorded on the run, part of
its input digest, and passed to an input named `seed` when the flow declares
one, so the number a run is labelled with is the one the code drew from.

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

docs/code/cli.md

@@ -180,7 +180,18 @@ the numbers the run reports as they arrive:
 ```
 
 Ctrl-C while either is waiting cancels the run on the engine rather than only
-stopping the watching, and exits 130.
+stopping the watching, and exits 130. `--timeout SECONDS` gives up *waiting*
+after that long and leaves the run going; it is nothing to do with a node's own
+timeout.
+
+`--seed N` is the experiment's seed, and it does three things. It is recorded
+on the run, so what a result came from is answerable later. It goes into the
+digest that identifies a run's inputs, so two runs of one configuration with
+different seeds are different runs rather than a cache hit. And if the flow
+declares an input named `seed`, that is what fills it — so the number the run
+is labelled with is the number your code actually drew from, instead of merely
+looking like it. A flow that declares no such input still records it, and
+nothing reads it. Sweep over seeds with `--param seed=1,2,3`.
 
 An input declared as an `artifact` takes the file a previous run produced,
 named rather than typed out:
@@ -234,8 +245,14 @@ 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.
+what is wrong if not, whether it is paired with a portal and reaching it, then
+every flow with its state, its node count and whether it has unpublished
+changes, and the last few runs and failures under them.
+
+The portal reads one of three ways. `no portal` means this installation was
+never enrolled. `portal hub.fluksio.com` means the link is up. `portal
+unreachable` names the error, and is the one worth acting on — the dashboard is
+served from the other end, so nobody can reach it while that is showing.
 
 `--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