Merge origin/main: reconcile the frank-zealot reslice with the dedupe pass

main moved under this campaign — PR #25/#26 resliced the RTX 3090 endpoint.
The frontmatter conflict is resolved in favour of the live shape, confirmed
by re-probe the same day: `--ctx-size 602112 --parallel 3` (3 × 200,704),
`--cache-type-k f16 --cache-type-v q8_0`, `--spec-type draft-mtp`, `--jinja
--reasoning auto`, `--metrics`. The 262,144 figures that remain on the page
are era rows and the checkpoint's trained window, not the live shape.

log.md's 2026-10-19 fleet-state bullet now records both probes and the law
this taught: a docs pass that reports live shapes must re-probe before
writing the number, because main moving mid-campaign makes the first probe
stale.

serverAppConfigs-docs/log.md

@@ -43,9 +43,15 @@
   holds `StillDeadcode`, `rad`, `tpl.jinja` — so the MXFP4 checkpoint that two
   pages called the "on-disk rollback" is a re-fetch, now stated once, on the era
   page that owns that payload.
-- **Fleet state confirmed live, not from files**: frank-archon 3 × 200,000 fp8 KV,
-  frank-dragoon 2 slots × 200,704, frank-zealot 2 × 262,144; all three answer
-  `/health` 200 and every env value matches its page.
+- **Fleet state must be probed, and probed again at the end.** The first pass read
+  frank-archon 3 × 200,000 fp8 KV, frank-dragoon 2 × 200,704, frank-zealot
+  2 × 262,144 and every env value matched its page. `origin/main` then moved under
+  the campaign — PR #25/#26 resliced frank-zealot — and the live re-probe on the
+  same day says **`--ctx-size 602112 --parallel 3` ⇒ 3 × 200,704, f16 K + q8_0 V,
+  `--spec-type draft-mtp`, `--jinja --reasoning`, `--metrics`**, matching
+  [[frank-zealot]] exactly. **Law: a documentation pass that reports live shapes is
+  stale the moment main moves; re-probe `/slots` and the running cmdline before
+  writing the number, not after.**
 
 ## 2026-10-18
 - **frank-zealot resliced to two windows of exact KV (Frank's call, PR #21).**