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-radiance-swift15-w4dn8.md

@@ -547,14 +547,16 @@ full-height conversations at once, and answer each one exactly. It does.
 
 ### Wire rename + the bench drop-in trap (2026-10-09)
 
-`FRANK_ARCHON_SERVED_NAME` moved `frank-archon` → **frank-archon**; the
-service, unit, scripts and env file keep the old name. Radiance is the only
+`FRANK_ARCHON_SERVED_NAME` moved the served id `frank-primary` →
+**frank-archon** (commit `7c77326`, 2026-10-09); the service, unit, scripts and
+env file kept `frank-primary` until the 2026-10-10 rename (`55f87fc`) brought
+them to `frank-archon` too. Radiance is the only
 fleet engine whose `/v1/models` listing reflects the flag, and it echoes the
 **requested** model name in chat responses — so a chat probe that returns 200
 proves nothing about the served id. Always read `/v1/models`.
 
 The first deploy after the edit came up green and `/v1/models` still said
-`frank-archon`. Cause: a campaign leftover drop-in
+`frank-primary`. Cause: a campaign leftover drop-in
 `/etc/systemd/system/frank-archon.service.d/bench.conf` (2026-10-08 04:09)
 overrode BOTH `Environment=FRANK_ARCHON_ENV_FILE` and `ExecStart` to the
 staging worktree `/home/dank/serverAppConfigs-swift15`. Every
@@ -563,7 +565,8 @@ staging tree: green health gate, old configuration, silently. Verified before
 removing: the staging `serve-frank-archon.sh` and `frank-archon.service`
 are byte-identical to the checkout, its `frank-archon.env` differed only by
 the alias line, and its HEAD (`8375567`) is an ancestor of `main`. The
-drop-in is staged in `/home/dank/.AGENTTRASH/20261009-frank-archon-bench-dropin/`.
+drop-in was staged in `/home/dank/.AGENTTRASH/20261009-frank-archon-bench-dropin/`
+(that dated dir is gone — the trash dir is empty on Dankserver as of 2026-10-18).
 After `daemon-reload` + restart, `/v1/models` reports `frank-archon` (boot
 healthy in 102 s, shape unchanged: fp8 KV, spec depth 2, seqs 3, vram pair
 26071/3543).