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/frank-medium-llamacpp-dflash2.md

@@ -312,7 +312,7 @@ came up healthy and *text-only*: image requests answered 500 "image input is
 not supported — hint: … provide the mmproj" and the load log had no mmproj
 line, so `llama-server` fb27a525 does not pick up `mmproj*.gguf` from the
 model directory. The serve script now passes `--mmproj` explicitly (the
-frank-secondary pattern), refuses to start without the file when vision is on, and
+frank-zealot pattern), refuses to start without the file when vision is on, and
 the deploy handler's preflight checks for it. Verified end-to-end after the
 fix: a generated 64x32 test image was described from its pixels — with
 thinking on the model reasoned about "the three horizontal bars" (its reading
@@ -724,7 +724,7 @@ fleet.
   2026-09-15, whose `--split-mode layer` measurements this service reuses
 - [[Dual-R9700-Cooperation]] — why the two cards cannot take part in a
   collective, and every software escape that is closed
-- [[frank-secondary-qwen38-gsq-rco]] — the fleet's other llama.cpp endpoint (RTX
+- [[frank-zealot-qwen38-gsq-rco]] — the fleet's other llama.cpp endpoint (RTX
   3090, MTP, the image path)
 - [[Dankserver System Specs]] — hardware inventory
 - [[frank-medium-batch-ubatch]] — the batch/ubatch sweep that set the deployed