docs(vault): service and infrastructure pages stop restating endpoint facts

18 pages cut their per-endpoint shape, payload, port and window claims and
link [[frank-archon]] / [[frank-dragoon]] / [[frank-zealot]] instead. Several
of the cut claims had already drifted -- the stack page still described the
kingjones ROCmFP4 era on ROCmFPX, OpenWebUI carried the 27B/3-slot bench
narrative, Hermes named a retired max_model_len and the old service name, and
the OMP harness page's live-window block had drifted off frank-zealot's real
262,144 (it is now labelled a dated worked example whose authority is the
endpoint page).

Two facts gain a single owner instead of two: the up{job=~"frank-.*"} scope
lives in Infrastructure/Prometheus.md, and the blackbox/Anubis probe form in
Architecture/Stale Signal Audit.md, each cited from the other page.

Voice Packs and Frank TTS carried live-state claims that contradicted the
engine page's 2026-10-18 deploy record (nothing listening on 7772/8880, model
dir absent); they now point at the pages that own host state.

serverAppConfigs-docs/Operations/Container Host Reachability.md

@@ -94,8 +94,8 @@ earlier can still hold listener/TIME_WAIT state, so the replacement dies
 `pasta: ... bind: Address already in use` (conmon exit 126) — then **self-heals
 seconds later** under `Restart=on-failure`. The failure looks like it failed,
 then looks fine, and the missing gate stays invisible because the retry masks
-it. Observed 2026-09-16 cutting `frank-dragoon` from a root unit to a rootless
-Quadlet.
+it. First seen on a `frank-dragoon` unit cutover; which supervision shape that
+era was is in [[frank-dragoon]]'s era table.
 
 Gate procedure: stop the old unit AND the new one (a redeploy's running
 replacement is itself the port-holder — without that stop the gate deadlocks