diff --git a/serverAppConfigs-docs/log.md b/serverAppConfigs-docs/log.md
index f6d144e..3c76e97 100644
--- a/serverAppConfigs-docs/log.md
+++ b/serverAppConfigs-docs/log.md
@@ -1852,3 +1852,16 @@ every restart since the cutover.
   (`zealot.warn == dragoon.warn`) retired with the payload it described.
   The CRACK re-export (byte-identical geometry per header census) stays on
   disk as the one-line `MODEL_FILE` fallback if refusals bite.
+- **Deployed 19:44** (`--service frank-zealot --service homepage`): production
+  boot reproduced the census exactly — 22,664 used / 1,461 free, fit projected
+  21,439 leaving 2,119 ≥ 1,872, KV 13,328.00 MiB at `n_ctx_seq = 200,704`,
+  `n_slots = 2`, projector loaded, alias `frank-zealot` on `/v1/models`. Live
+  probes: exact `pong` + `reasoning_content`, `tool_calls` `{"city":"Seattle"}`,
+  512 px PNG → **Red**, 75.8 t/s decode (1 % off the trial arm). e2e 33/33.
+- Two live-path stragglers the cutover also had to catch: `serve-frank-zealot.sh`
+  still DEFAULTED to the 9B paths and f16 KV (a defaulted run would have served
+  the retired payload — now re-keyed to the shipped trio), and the OpenWebUI
+  `model` row's `meta.description` is live DB state naming the 9B (re-keyed,
+  backup `webui.db.bak-20261017a`; no `open-webui` restart forced — the cached
+  list picks it up on the next one, and forcing it logs every family session
+  out for one cosmetic string).