frank-medium: deploy two single-GPU replicas — TP=2 is blocked by PCIe atomics

The radiance MXFP4 stack cannot run TP=2 on this host. RCCL's collective
kernels carry a hidden hostcall-buffer parameter, and ROCr refuses to
dispatch them on a device without PCIe atomics: the AQL dispatch fails with
hipErrorIllegalState ("the operation cannot be performed in the present
state"), which is what every two-rank collective hit. The second R9700 sits
behind the chipset bridges 05:00.0/06:09.0, which advertise
`AtomicOpsCap: Routing-` — a read-only capability, so no software can enable
atomic routing on that path and the driver's
pci_enable_atomic_ops_to_root() fails for that card. The first card, on CPU
root port 00:01.1, has atomics enabled.

Ruled out: kernel version (7.0.0-28/-30/-31 identical, after a full upgrade),
iommu=pt, P2P hardware (45.3 GB/s between the cards), the shipped librccl (a
from-source rebuild reproduces the failure at the same call path), vLLM and
pynccl (a bare two-rank torch.distributed allreduce fails the same way), all
NCCL transport knobs, and single-rank tests (NCCL short-circuits at
world_size=1, so one-card success proves nothing).

Deployment: three rootless Quadlets — frank-medium-a (:7771, card 1),
frank-medium-b (:7772, card 2), both TP=1 at 114688 context (262144 and
131072 do not fit one card's KV) with vLLM-profiled KV — and
frank-medium-proxy (:7770), a round-robin that preserves the fleet contract
of one endpoint and one served model name. frank-medium.container stays as
the TP=2 target for a host whose second card is atomic-capable; the deploy
handler does not install it and trashes any stale copy.

Measured through the proxy (vllm bench serve, random dataset, --ignore-eos):
conc 1 42.8 tok/s, conc 4 147.6 tok/s, conc 8 230.8 tok/s, 32k prefill at
~2.8k tok/s per card, TPOT p50 23.6-28.8 ms.

Also: healthcheck reads PORT so one probe serves all three units, the hermes
example and the harness models.yml drop to the real 114688 context, and the
runbook records the full evidence chain.

dankserver/frank-medium/quadlet/frank-medium.container

@@ -19,6 +19,15 @@
 # what this unit does too — no PublishPort. The fleet contract is unchanged:
 # :7770, served model name frank-medium (SERVED_NAMES), OpenAI /v1.
 #
+# NOT INSTALLED ON THIS HOST. This is the target shape: one tensor-parallel
+# process across both R9700s. It cannot launch a collective here — RCCL's
+# kernels need PCIe atomics and the second card sits behind chipset bridges
+# advertising `AtomicOpsCap: Routing-` — so the active deployment is the
+# two-replica trio in this directory (frank-medium-a/b/proxy) and
+# deploy-remote.sh deliberately does not install this unit. Keep it for a
+# host whose second card is on an atomic-capable root port; the full evidence
+# is in serverAppConfigs-docs/LLM/frank-medium-radiance-mxfp4.md.
+#
 # DEVICES. /dev/kfd + /dev/dri through the amdgpu/KFD stack; HIP/ROCR device
 # indices 0,1 (the two R9700s). The 2 GiB Raphael iGPU enumerates as index 2
 # and is excluded both by the index pin and by the upstream MIN_GPU_MIB=8192