docs(vault): fleet-wide fact re-verification pass (67 pages)

The docs-fact census wave re-read the live hosts and re-keyed every page
it could: runtime/payload identities, ports, sizes, ledger figures, unit
state, and the retirement banners that drifted as the fleet moved. The
wave was interrupted mid-run, so this commit carries only what passed the
integrity gates: every touched page parses (front matter or H1+status
convention intact, balanced fences, no truncated tables, trailing
newline), the docs_completeness and link-integrity seams are green, and
bats is 384/384.

Numbers that this session proved on live hosts are keyed to the measured
value, not the page's earlier claim.

serverAppConfigs-docs/LLM/Model Swap and Rollback.md

@@ -251,17 +251,24 @@ step a redeploy deadlocks against its own gate.
 small/fast + image roles at the new endpoint; move the vision role WITH the
 vision tower (one owner per capability). `shared/homepage/services.json`: a
 card per endpoint, probed from the monitor's own host. Prometheus: only add
-a job if the runtime actually exposes Prometheus text (halogen publishes
-`/health`, `/cache`, `/v1/*` and nothing else — the job was REMOVED with the
-reason written down rather than left as a permanent red).
+a job if the runtime actually exposes Prometheus text — and re-measure rather
+than repeat, because that answer moves. This bullet once said halogen serves
+`/health`, `/cache`, `/v1/*` "and nothing else"; measured 2026-10-18 on
+Dankclaw, `curl -s http://127.0.0.1:7770/metrics` returns Prometheus text
+(`# HELP llamacpp:prompt_tokens_total …`, content-type
+`text/plain; version=0.0.4`) while an invented path 404s — so the surface has
+grown and a scrape target is expressible again.
 
 **4. Cutover, then verify by driving it.** `deploy.sh <target> --service
 <large> --service <small>` (order matters); per endpoint: `/health`,
 `/v1/models` reports the alias, a chat completion returns content AND
 `reasoning_content`, a `tools` request returns `tool_calls`, an image
 request is answered (or refused with a named reason), the runtime's own
-speculation counters move, and the unit is `enabled`/`generated` with linger
-on. Read the engine's boot ledger for a silent clamp. Finally spend one
+speculation counters move, and the unit is `enabled` and `active`. All three LLM
+endpoints are **root** units today (`User=dank` + `WantedBy=multi-user.target` —
+`scripts/frank-archon.service:30,71`, `scripts/frank-dragoon.service:8,31`,
+`scripts/frank-zealot.service:8,26`), so linger is not what gates them; linger
+matters for rootless quadlets. Read the engine's boot ledger for a silent clamp. Finally spend one
 real request through the harness per changed role — routing labels lie; the
 servers' own journals do not.
 
@@ -278,4 +285,4 @@ predecessor "stopped" (the port race above).
 - [[Llama Cpp Serving Sizing]] — pricing the shape once it loads
 - [[RDNA4 MoE Expert Offload VRAM Budget]] — vLLM-side fit arithmetic
 - [[LLM Bench Windows and Measurement]] — measuring the new deployment
-- [[dankserver-qwen38-fp8-expert-offload-tuning]] — the current endpoint
+- [[dankserver-qwen38-fp8-expert-offload-tuning]] — the retired tcclaviger vLLM endpoint (2026-09-29 → 10-05); the live Dankserver endpoint is [[frank-archon-radiance-qwen38-iq4r]]