docs(vault): service and infrastructure pages stop restating endpoint facts

18 pages cut their per-endpoint shape, payload, port and window claims and
link [[frank-archon]] / [[frank-dragoon]] / [[frank-zealot]] instead. Several
of the cut claims had already drifted -- the stack page still described the
kingjones ROCmFP4 era on ROCmFPX, OpenWebUI carried the 27B/3-slot bench
narrative, Hermes named a retired max_model_len and the old service name, and
the OMP harness page's live-window block had drifted off frank-zealot's real
262,144 (it is now labelled a dated worked example whose authority is the
endpoint page).

Two facts gain a single owner instead of two: the up{job=~"frank-.*"} scope
lives in Infrastructure/Prometheus.md, and the blackbox/Anubis probe form in
Architecture/Stale Signal Audit.md, each cited from the other page.

Voice Packs and Frank TTS carried live-state claims that contradicted the
engine page's 2026-10-18 deploy record (nothing listening on 7772/8880, model
dir absent); they now point at the pages that own host state.

serverAppConfigs-docs/Operations/Payload and Disk Reclaim.md

@@ -48,8 +48,9 @@ table. Three buckets:
   re-download.
 - **retired** — maps to a retired runtime. Safe candidates.
 
-Trap: a directory can hold **both** a dead target and a live drafter
-(frank-dragoon's DFlash2 drafter lives beside the previous target). Move the
+Trap: a directory can hold **both** a dead target and a live asset — an era's
+drafter can sit beside the retired target it came with (per-endpoint era tables:
+[[frank-dragoon]], [[frank-zealot]], [[frank-archon]]). Move the
 single file, never the directory, and say so in the manifest.
 
 ## 3. The live-reference check — before moving anything
@@ -149,13 +150,13 @@ name**, never `endswith('.gguf')` — mradermacher ships large quants as
 
 ## Refresh per engine — know the recovery path BEFORE deleting
 
-- **frank-dragoon (halogen)**: the engine fetches its own payload via
-  `HALOGEN_DOWNLOAD` when the checkpoint is absent. Clear the directory but
-  leave it **existing and empty**, then start the unit. **Bind-mount trap:**
+- **frank-dragoon**: self-fetching — clear the directory but
+  leave it **existing and empty**, then start the unit; the download knobs and
+  the payload's byte count (which is what the re-download costs) are on
+  [[frank-dragoon]]. **Bind-mount trap:**
   podman refuses a mount whose source is missing
   (`Error: statfs /home/dank/models/halogen: no such file or directory`) and
-  the unit loops on `Restart=on-failure` — `mkdir -p` the empty dir. ~124 GiB
-  at 130–240 MB/s ≈ 10–20 min, then load.
+  the unit loops on `Restart=on-failure` — `mkdir -p` the empty dir.
 - **llama.cpp services**: no self-fetch; the serve script refuses to start
   without weights. Pull yourself and verify: