llm: retire the trio service names — fleet services renamed to frank-archon/frank-dragoon/frank-zealot

The 2026-10-09 wire aliases become the service names everywhere:
systemd units, serve scripts, env files and FRANK_* variables,
deploy-plan/deploy-remote service keys, container names, Prometheus
job names + alert rules, Grafana dashboard queries, bats seams,
runbook filenames, homepage/AGENTS lore, and historical prose.
Rollback tags renamed in lockstep. Residue in the tree: zero.
Retired frank-medium/small/npu names are history and stay.

Known casualty: scripts/patches/*.patch context lines were rewritten;
those retired-era vLLM-fork patches no longer apply byte-exact.

serverAppConfigs-docs/LLM/Llama Cpp Serving Sizing.md

@@ -80,7 +80,7 @@ co-tenants.
 - **Traps:** mmap'd PLE is reclaimable page cache; `-ot` makes it pinned —
   "move layers to the card" converts reclaimable cache into device memory and
   frees nothing for co-tenants. A served model's footprint ≠ weight size
-  (frank-secondary: 22.6 of 24.1 GiB for an 11.29 GiB model). Do the capacity
+  (frank-zealot: 22.6 of 24.1 GiB for an 11.29 GiB model). Do the capacity
   subtraction before designing: 12 attn layers × 1.62 GiB + 200k f16 KV =
   28.6 GiB > 24.1 GiB usable → KV-in-VRAM on that pair only reaches ~64k.
 - **Context lengths: derive, never remember.** `llama-bench` computes
@@ -157,7 +157,7 @@ in the timings. Context cap for full-model residency on that shape stayed
 ## Related
 
 - [[GGUF Compatibility]] — what a payload is before it is priced
-- [[frank-secondary-llama-mimo-q6k-2x200704]] — the current two-boot priced shape
+- [[frank-zealot-llama-mimo-q6k-2x200704]] — the current two-boot priced shape
 - [[frank-medium-llamacpp-dflash2]] — where the 68 KiB/token datum was measured
 - [[DFlash DSpark Speculative Decoding]] — the spec A/B protocol on llama.cpp
 - [[Dual-R9700-Cooperation]] / [[x4-pair-experiment]] — the multi-device side