docs(log): record the service-rename cutover outcome and the zealot --metrics gap

serverAppConfigs-docs/log.md

@@ -19,6 +19,22 @@
   `scripts/patches/` carry the old service names in context lines; the
   sweep rewrote them, so those patches (retired eras, rebuildable from
   the renamed tags) no longer apply byte-exact.
+- **Executed live at `55f87fc`, all three gates green.** Per host: stop
+  old unit → trash its deploy-state marker + remove the unit symlink and
+  old container → `deploy.sh <host> --service <new-name>`. Result:
+  `frank-archon` active/enabled (container `frank-archon`, :7770),
+  `frank-dragoon` active/enabled (container `frank-dragoon-halogen`,
+  :7770), `frank-zealot` active/enabled (journal shows 87–93 t/s serving
+  compaction on :7771). `/health` 200 ×3; `/v1/models` reports the three
+  ids; host checkouts grep zero residue; e2e passed 32+1flaky, 32+1flaky,
+  33; Prometheus `frank-archon`/`frank-dragoon` up.
+- **Pre-existing gap found by the verification, NOT a rename regression:**
+  `frank-zealot` `/metrics` answers 501 — llama.cpp gates the endpoint
+  behind `--metrics` (default disabled) and the serve script never passed
+  it, so `up{job="frank-secondary"}` had NO series at all in the last 24 h
+  (the zealot metrics + the queue-depth alerts on it have been dead since
+  the Qwen3.5 swap). Fix = one flag in `serve-frank-zealot.sh` + a ~1 min
+  zealot restart; not applied in the rename window.
 
 ## 2026-10-09
 - **Live — five authentik human accounts provisioned (Dankclaw, `ak shell`