Close eight open SDK tasks: the pidfile, the log, cards, names and a live curve

Each was a loose end recorded under `### SDK` in the notepad.

`serve` takes its own pidfile down on SIGTERM. uvicorn restores the handler it
found and re-raises the signal it stopped on, so the default handler ended the
process without unwinding and the `finally` never ran — which is what a stop
sends, and what left `serve.pid` behind.

`serve.log` is cut back past 5 MB by the engine rather than by the screen that
started it, so an adopted engine is bounded too. Gated on its own stdout being
an appended regular file, which is what makes the cut safe: the kernel then
puts the next write at the new end.

Cards are counted from `/dev/nvidia[0-9]*`, so `FLOW_GPUS`/`--gpus` of 0 means
"work it out" the way `FLOW_CPUS` always has. The engine counts, not the
accountant — a remote worker builds one of those from its own inventory, and
detecting there would hand it the engine host's cards. The worker counts last:
what a batch job says it was granted still wins.

`GET /runs/metrics/names` is the distinct over a selection that `--list` and
the terminal's metric picker were approximating by reading the newest run that
had measured anything, which missed a name only an older run ever wrote.

`MetricSink` announces each batch it has written (`run_metric`, carrying the
names). Not a per-point event: one covers up to 500 points or two seconds of
them, and the rows stay the record. The terminal comparison fills in as the
first readings land instead of staying blank until reopened, and the browser
refetches the run and any comparison rather than the list behind them.

`retry --group` pages the list route by `before` instead of stopping at 500.

The terminal dashboard takes the terminal's colours (`ansi-dark`), and the web
UI can re-pair from Settings without disconnecting first.

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

frontend/src/components/Flow/useFlowSocket.ts

@@ -109,6 +109,13 @@ type FlowEvent =
       group?: string
       ts?: number
     }
+  | {
+      type: "run_metric"
+      flow: string
+      run: string
+      names: string[]
+      ts?: number
+    }
 
 function socketUrl(): string {
   const base = String(OpenAPI.BASE || window.location.origin)
@@ -328,6 +335,14 @@ function connect() {
         // live value, so nothing here goes through the live store.
         client?.invalidateQueries({ queryKey: runKeys.all })
         break
+      case "run_metric":
+        // A batch of readings was written. Only what draws them is refetched —
+        // the run's own detail (its metric names and curve hang below that
+        // key) and any comparison — so a training run reporting every second
+        // does not re-read the list behind it.
+        client?.invalidateQueries({ queryKey: runKeys.detail(message.run) })
+        client?.invalidateQueries({ queryKey: runKeys.compares })
+        break
     }
   }