docs: frank-medium is llama.cpp with DFlash2 on both cards

The runbook for the new deployment, plus the sweep of everything that still
described the vllm-radiance replica pair: the vault index and its ACTIVE
marker, the superseded banner on the radiance page, the pointer from the
ROCmFPX page, the homepage card, the Grafana dashboard description and the
observability page's scrape table.

The new page carries the two facts a future agent needs and the flags do not
say: llama.cpp's layer split is what lets BOTH cards serve ONE model without
any collective (vLLM's PP handoff is an RCCL send/recv, which is the primitive
this host cannot dispatch), and the rocBLAS Tensile-path trap that makes a
healthy-looking build fail on the first request.

serverAppConfigs-docs/LLM/frank-medium-radiance-mxfp4.md

@@ -16,6 +16,12 @@ tags:
 timestamp: 2026-09-16
 ---
 
+> **SUPERSEDED 2026-09-16.** This page is the record of the retired
+> vllm-radiance MXFP4 deployment. The ACTIVE frank-medium is mainline
+> llama.cpp with the DFlash2 drafter ([[frank-medium-llamacpp-dflash2]]);
+> the PCIe-atomics evidence in this page remains the reason the runtime is
+> layer-split llama.cpp rather than tensor-parallel vLLM.
+
 # frank-medium vllm-radiance MXFP4 Runbook
 
 The ACTIVE frank-medium deployment (since 2026-09-15/16): the