phase: 34_radiance_llm_engine

Everything is verified and green. Final report:

**Phase 34 final verification pass — complete**

- Verified all 6 completed tasks' work against the live fleet and hermetic suite: `llm:radiance` job registered, `llm_engines()` registry drives 404 gate / history defaults / `/api/config` (additive, byte-identical gufo/vllm keys), radiance field map + `/stats` sidecar + 7-position spec curve, `/llm` strip/curve/rows.
- **Defect found & fixed (pre-existing, task 05):** the vLLM-only sentence "vLLM exposes no per-slot JSON…" rendered on the **radiance** panel (`slotSection`'s non-gufo branch). Fix: vLLM line gated to `engine === 'vllm'`; radiance's panel slot section renders nothing (its session home is the strip) — `page-llm.js` + the served-byte pin in `tests/test_api.py` (now asserts the radiance branch is empty and the sentence can't leak). Browser-verified; re-shot `data/logs/34-llm-radiance-rest.png` (the 4.5-min wait found no in-flight request, so the busy shot remains the earlier pass's — its strip rows still stand; only the panel text predates the fix).
- Tests: `uv run pytest` → **2031 passed, 19 skipped** (100%); `uv run pytest --cov` → **98.73%** (floor 94%; config 100%, llm 99%, collectors 98%, api 99%); `uv run ruff check src tests agent && uv run pyright` → clean; `node --check` OK; `uv pip list --outdated` → empty.
- `uv run pytest -m live --live` → **13 passed, 2 skipped** (vLLM unset — correct; live-write opt-in — correct); the read-only radiance test passed.
- Completion criteria: (1) engines `gufo`+`radiance`, `fleet.engines_live` 2, `config.llm.radiance.enabled` true — **pass (live curl)**; (2) unset → 404 no-dial + no job — **pass (spy-pinned, green)**; (3) fixtures present, both families (79 `radiance:` / 198 `vllm:` lines), drift pin — **pass**; (4) panel/curve/rows — **pass (re-shot rest screenshot)**; (5) live radiance test — **pass**; (6) suite/coverage/lint/`bash .agents/validate.sh` (exit 0) — **pass**; (7) docs — below; (8) gufo/vLLM behaviour unchanged — **pass (existing pins untouched)**.
- Documentation: **README.md** full review — env table, LLM-engines section, architecture diagram, capture-script and `/llm` section all name radiance correctly; no inconsistencies found, no changes needed. **AGENTS.md** — the three task-06 fixes (fleet line, route row, module bullets) are in place and all other statements match reality; no changes needed.
- Dev server healthy (`./scripts/dev-server.sh status`: all sources ok, `llm:radiance` answering); all changes left in the working tree for the harness.
- Next pending phase: none — 34 was the last phase in `todo/`.

AGENTS.md

@@ -26,7 +26,7 @@ file — plus an overview page:
 | `/`        | Is anything wrong, and where do I look first?                  | all five, in one request                                       |
 | `/system`  | CPU, memory, disk, GPU, network, and the history               | `agent/host_agent.py`, our own stdlib agent per host           |
 | `/disks`   | Are any physical disks failing, and which — health, temp, wear | the same agents, `smartctl -i -A -H` per whole drive          |
-| `/llm`     | Tokens/s, active sessions, queue depth, KV pressure, latency   | gufo `/metrics` + `/slots`, vLLM `/metrics`                   |
+| `/llm`     | Tokens/s, active sessions, queue depth, KV pressure, latency   | gufo `/metrics` + `/slots`, vLLM `/metrics`, radiance `/metrics` + `/stats`  |
 | `/ups`     | Battery health, runtime left, power events, test buttons       | NUT `upsd` (our own wire client; port **3051**, not 3493)    |
 | `/gateway` | Which domains on which port, and where each goes               | the same agent's `haproxy` + `nginx` sections joined to `/proc/net/tcp{,6}` on the one `GATEWAY_HOST` host (the page needs agent **≥ 1.2.0**; the route switch's `#off` marker read is **1.4.0**) |
 
@@ -164,7 +164,9 @@ One line each — the load-bearing behaviour is in the bullet, the rest is in th
   agent's: `ROUTE_MARKER` / `split_marker` / `config_line_index` — `disabled` on
   `server`/`proxy_pass`/`map` nodes; a marked line stays in the document).
 - `config.py` — env only, no config file format, no CLI flags. `.env` is a *seed*; a real
-  env var always wins. Safe defaults except the sources, which default to unset. The
+  env var always wins. Safe defaults except the sources, which default to unset
+  (`HOST_TARGETS` and the engine URLs `GUFO_BASE_URL` / `VLLM_BASE_URL` /
+  `RADIANCE_BASE_URL`, each with its optional `*_API_KEY`). The
   gateway source is enabled only when `GATEWAY_HOST` names a `HOST_TARGETS` entry
   (default `gateway`). The write's two settings are beside it: `GATEWAY_ALLOW_WRITES`
   (default **off**, the NUT flag's truthy rule) and `GATEWAY_WRITE_TIMEOUT_SECONDS`
@@ -214,8 +216,9 @@ One line each — the load-bearing behaviour is in the bullet, the rest is in th
   same shape from a hand-deleted line still warns; the switch-off tally is published
   as `/api/summary`'s `disabled` field. No `severity` anywhere in the payload (a busy
   proxy is the job).
-- `sources/llm.py` — gufo + vLLM field maps, measured Δ rates **diffed per label set**,
-  prefill speed, the session list from gufo `/slots`. A refused estimator window is still
+- `sources/llm.py` — the gufo / vLLM / radiance field maps, measured Δ rates **diffed per label set**,
+  prefill speed, the session list from gufo `/slots` (radiance's from its `/stats`
+  sidecar). A refused estimator window is still
   an answer: the cell keeps its `source` and an honest `Δ<window>` beside a `null`.
 - `sources/nut.py` — the NUT wire client, `assess()` (explicit checks, not a mystery
   score), `SELF_TEST_OUTCOMES`, the `COMMANDS` catalog with risk tiers and
@@ -296,7 +299,7 @@ Treat the scheme as a public interface of the history API.
 
 | Host          | ssh           | What it gives                                                             |
 | ------------- | ------------- | ------------------------------------------------------------------------- |
-| `driveripper` | `driveripper-ops` | Threadripper 24c/48t + Radeon AI PRO R9700, vLLM `:8000`, **upsd**, the dashboards. 16 whole disks; the agent unit runs `User=root` with `CapabilityBoundingSet=CAP_SYS_RAWIO CAP_SYS_ADMIN` (kernel 7.2's unprivileged-passthrough gate; an empty bounding set is capability-less, `CapEff 0`) |
+| `driveripper` | `driveripper-ops` | Threadripper 24c/48t + Radeon AI PRO R9700, radiance `:8000` (replaced vLLM there, 2026-10-24; the vLLM code and env var stay for other deployments), **upsd**, the dashboards. 16 whole disks; the agent unit runs `User=root` with `CapabilityBoundingSet=CAP_SYS_RAWIO CAP_SYS_ADMIN` (kernel 7.2's unprivileged-passthrough gate; an empty bounding set is capability-less, `CapEff 0`) |
 | `deskwork`    | `deskwork-ops`  | Strix Halo (Radeon 8060S iGPU), gufo `:8731`                               |
 | `gateway`     | `gateway-ops` | the router, the fleet's ingress: haproxy (`/etc/haproxy/haproxy.cfg`, six frontends → six backends) + nginx (`/etc/nginx/nginx.conf` plus `conf.d/` vhosts and `stream.d/`'s `map` on `:443`); runs agent **1.4.0** with the `dashboards-routectl` helper units |