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/Tcclaviger Fork Ops.md

@@ -10,9 +10,9 @@ timestamp: 2026-10-05T00:00:00-07:00
 
 The tcclaviger RDNA4 vLLM fork (`docker.io/tcclaviger/vllm@sha256:da4029666…`,
 vLLM 0.29.0.dev, GLM-5.3/Qwen-specialised with native MoE quant kernels and a
-first-class expert-offload planner) served `frank-primary` at shape G until
+first-class expert-offload planner) served `frank-archon` at shape G until
 the 2026-10-05 FreeToken cutover; it remains the rollback target
-(`git tag frank-primary-vllm-shapeG-20261003`). Full plan law and VRAM
+(`git tag frank-archon-vllm-shapeG-20261003`). Full plan law and VRAM
 arithmetic: [[RDNA4 MoE Expert Offload VRAM Budget]]; boot forensics:
 [[vLLM Boot Forensics and Config Interrogation]]; window discipline:
 [[LLM Bench Windows and Measurement]].
@@ -213,7 +213,7 @@ through two image tags to bring an overlay up was entirely wasted work.
 ## Compile-cache persistence (survives `podman rm -f`)
 
 Serve scripts that recreate the container discard the writable layer, so
-every boot re-pays compile/JIT (frank-primary: `torch.compile took 181.20 s`
+every boot re-pays compile/JIT (frank-archon: `torch.compile took 181.20 s`
 cold, of which 173 s was one graph).
 
 1. **Prove it and locate it:** fresh container vs live
@@ -241,7 +241,7 @@ cold, of which 173 s was one graph).
 ## Plan-line verification checklist (after any fork deploy)
 
 ```
-ssh dankserver 'sudo journalctl CONTAINER_NAME=frank-primary-qwen -b -o cat --no-pager \
+ssh dankserver 'sudo journalctl CONTAINER_NAME=frank-archon-qwen -b -o cat --no-pager \
   | grep -aoE "(budget \(total x util\) +[0-9.]+|expert cache space +[0-9.]+ GiB +[0-9,]+ slots|Estimated CUDA graph memory.{0,80}|Graph capturing finished.{0,40}|GPU KV cache size.{0,90})"'
 ```
 
@@ -250,7 +250,7 @@ these columns to `17.`. Verify: new budget/graphs/arena in the plan;
 `GPU KV cache size` matches the requested token count; `Estimated CUDA graph
 memory` vs the capture line (raise `_PER_GRAPH_MB` toward 52 if capture
 exceeds the charge); `rocm-smi --showmeminfo vram` high-water per card = the
-real margin; `systemctl show frank-primary -p NRestarts --value` = 0;
+real margin; `systemctl show frank-archon -p NRestarts --value` = 0;
 `VLLM_CUDAGRAPH_*` present in `podman exec … env`; then a real chat
 completion from a PEER — `curl localhost:7770/health` inside an ssh session
 on the host can return `000` and looks like an outage that isn't.