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/Dankclaw/Swap Configuration.md

@@ -33,10 +33,10 @@ it is not invisible.
 
 ## Why 64 GiB
 
-Dankclaw is shared. `frank-large` alone holds **103.5 GiB of the 121.2 GiB**
+Dankclaw is shared. `frank-dragoon` alone holds **103.5 GiB of the 121.2 GiB**
 host (`68.0 weights + 14.4 KV pool + 21.1 working`), leaving roughly
 **7.1 GiB** for 28 co-tenant containers whose working set is ~4.3 GiB. The
-engine itself warns that when that runs out, frank-large and its neighbours
+engine itself warns that when that runs out, frank-dragoon and its neighbours
 "can stall for minutes at a time at full CPU with no disk activity and no
 output". Swap is the valve that turns an OOM kill into slow paging.
 
@@ -96,20 +96,20 @@ Then confirm the inference service is unaffected — a completion, not just
 ```bash
 curl -s http://127.0.0.1:7770/v1/chat/completions \
   -H 'Content-Type: application/json' \
-  -d '{"model":"frank-large","messages":[{"role":"user","content":"Reply with exactly: SWAP64-OK"}],"max_tokens":48,"reasoning_effort":"low"}'
+  -d '{"model":"frank-dragoon","messages":[{"role":"user","content":"Reply with exactly: SWAP64-OK"}],"max_tokens":48,"reasoning_effort":"low"}'
 ```
 
 As run 2026-09-12: `finish_reason: stop`, `SWAP64-OK`, 28 containers up,
-frank-large `health=200` throughout.
+frank-dragoon `health=200` throughout.
 
 ## Caveats
 
-- **Swap cannot help the pinned weights.** frank-large's ~68 GiB of weights are
+- **Swap cannot help the pinned weights.** frank-dragoon's ~68 GiB of weights are
   held deliberately; paging them is a stall, not a relief. More swap does not
   make the doubled KV pool affordable — see the reserve/pool ceiling in
   [[halogen-flash-server]].
 - **`vm.swappiness=60` is untested against this workload.** Under real
-  pressure the kernel will happily page anonymous memory, and frank-large's KV
+  pressure the kernel will happily page anonymous memory, and frank-dragoon's KV
   pool and working set *are* anonymous. Swapping the KV pool would be far worse
   than the OOM kill it prevents. If the box ever starts thrashing, lowering
   swappiness (or capping the engine's cgroup) is the knob, not more swap.