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/frank-archon-r9v-radiance-qwen38-uncensored.md

@@ -13,23 +13,29 @@ tags: [llm, frank-archon, r9v, vllm, radiance, gfx1201, retired]
 # frank-archon — R9V radiance-vLLM (dankserver, RETIRED)
 
 > **RETIRED 2026-09-27** — superseded the same day by the Q8_0 cutover,
-> [[frank-archon-r9v-radiance-qwen38-q8]]. Kept as the rollback runbook:
-> the uncensored state dir, frozen config and payload are intact on disk;
-> the rollback procedure lives in that page's Ops section.
+> [[frank-archon-r9v-radiance-qwen38-q8]] (itself retired 2026-09-30; the live
+> frank-archon runbook today, 2026-10-18, is
+> [[frank-archon-radiance-qwen38-iq4r]]). The uncensored state dir and frozen
+> config are still on disk (`/home/dank/r9v-state/uncensored/` — `setup.json`,
+> `restore-config-20260927.env`); the IQ4_XS **payload is not** — it was deleted
+> in the 2026-10-17 cleanup. The rollback procedure lives in the Q8_0 page's Ops
+> section, with a re-fetch as step one.
 
-The Dankserver LLM endpoint is the **R9V radiance-vLLM fork**
+The Dankserver LLM endpoint **was** the **R9V radiance-vLLM fork**
 (`drwolfen/radiance-vllm-qwen4exp`, docker-pinned prebuilt) serving
 `Dyluhn/Qwen3.8-Flash-Next-Uncensored-R9V-IQ4_XS` — the abliterated
 Qwen3.8-Flash-Next at IQ4_XS (92.39 GiB, 3 GGUF shards) with the blockfp8
 MTP4 head and the F16 mmproj — on **both R9700s** (gfx1201, BDFs
-`0000:03:00.0` / `0000:07:00.0`) as `frank-archon` on **:7770**.
+`0000:03:00.0` / `0000:07:00.0`) as `frank-primary` on **:7770** (the
+`frank-archon` wire alias arrived 2026-10-09).
 
 Replaced llama.cpp b11030 (Qwen3.8-Flash-Next Q_8) on 2026-09-27 at Frank's
 direction; downtime window ~1 h 20 min (killed 02:47, healthy 04:11 PDT).
 Rollback target: [[frank-archon-llamacpp-qwen38-flash-next-q8]] — the
 llama.cpp trio (unit/env/serve) is at commit `4992e5a`+ (the repo-side
-wiring; host unit was the relinked one) and the GGUF payload stays on disk,
-so a rollback is a redeploy.
+wiring; host unit was the relinked one); the GGUF payload is no longer on
+disk (Dankserver's `/home/dank/models/` holds only `StillDeadcode`, `rad`,
+`tpl.jinja` as of 2026-10-18), so that rollback is a re-fetch plus a redeploy.
 
 ## Production shape (repo-tracked)
 
@@ -38,7 +44,7 @@ The repo carries a **thin** wiring; the engine shape lives on-host:
 | Piece | File | Law |
 |---|---|---|
 | Unit | `scripts/frank-archon.service` | Root unit, `User=dank`, `LimitMEMLOCK=infinity`, `ExecStop=podman stop -t 120 frank-archon-r9v`, `Restart=on-failure` |
-| Env | `scripts/frank-archon.env` | Production overrides ONLY: bind 0.0.0.0, :7770, alias `frank-archon`, container `frank-archon-r9v`, GPU BDFs |
+| Env | `scripts/frank-archon.env` | Production overrides ONLY: bind 0.0.0.0, :7770, alias `frank-primary` (the wire id became `frank-archon` on 2026-10-09), container `frank-archon-r9v`, GPU BDFs |
 | Serve | `scripts/serve-frank-archon.sh` | Layers setup state under repo env → execs the fork's own `scripts/launch.sh` via the docker→podman shim → `docker wait` |
 | Deployer | `scripts/deploy-remote.sh` `deploy_llm_archon` | Gates on setup state ready, image digest, PLE bytes, shard files; MainPID false-green check |