docs: dankserver board swap clears the PCIe-atomics wall

Reanalysis after the 2026-09-20 swap to an ASUS ProArt B850-Creator WiFi
NEO: both R9700s now sit on CPU GPP root ports (x8/x8 Gen5 bifurcation),
every bridge reads AtomicOpsCap Routing+, and both endpoints read
AtomicOpsCtl ReqEn+ (CAP_EXP+28.w = 0x1440) — the exact precondition
Dual-R9700-Cooperation's test plan named. TP=2 is therefore unblocked,
not proven: no collective has been dispatched since the swap,
GGML_HIP_RCCL is still OFF, and the 272 t/s "tensor" number on record
measured a butterfly fallback.

- Dual-R9700-Cooperation: short answer rewritten, re-measured 2026-09-20
  topology table, rebuild-hypothesis door marked moot, probe plan is now
  standing work.
- Dankserver System Specs: Motherboard section; GPU BDFs 0b:00.0 ->
  07:00.0, iGPU 10:00.0 -> 11:00.0, kernel 7.0.0-31, SMT on, and the new
  eno2 (192.168.0.247) second 5GbE port holding the low-metric default
  route while eno1 keeps the fleet's static .235.
- frank-medium-llamacpp-dflash2: rationale and hardware row split past
  from present; dated work-log sections stay as history.
- AGENTS.md + both indexes: no longer assert a wall that no longer exists.

Docs only; frank-medium stayed active and healthy throughout (verified
/health). ./tests/run.sh 331/331.

serverAppConfigs-docs/LLM/index.md

@@ -60,15 +60,17 @@ frank-small, port 7771]
   2026-09-16 (model swapped 2026-09-19): mainline llama.cpp serving
   orcarouter/Qwen3.8-27B-Uncensored-GGUF at Q8_0 with the z-lab DFlash2 Q4_K_M
   drafter on Dankserver's 2x Radeon AI PRO R9700, as ONE layer-split process
-  behind :7770 (tensor parallelism is impossible on this host — the second card
-  cannot dispatch an RCCL collective), balanced 32:33 over two 163,840-token
+  behind :7770 (tensor parallelism was impossible on the old board's second
+  card; the 2026-09-20 swap cleared that gate but the runtime still ships
+  RCCL-less and the collective is unprobed), balanced 32:33 over two 163,840-token
   slots
 - [[frank-medium-radiance-mxfp4]] — RETIRED 2026-09-16, one day after it was
   deployed: the vllm-radiance MXFP4 stack (stilldeadcode/vllm-radiance:0.9.3 +
   ggz14/radiance-vllm-mxfp4 patches) serving
   just1moremodel/Qwen3.8-27B-Uncensored-MXFP4-awq as two single-GPU replicas
   behind a round-robin proxy; kept as the record of the deployment it
-  succeeded, plus the PCIe-atomics evidence that rules out TP=2 on this host
+  succeeded, plus the PCIe-atomics evidence that ruled out TP=2 on the previous
+  board — that gate cleared on 2026-09-20, see [[Dual-R9700-Cooperation]]
 - [[frank-medium-rocmfpx]] — PRIOR frank-medium deployment (llama.cpp era,
   2026-09-15): charlie12345/ROCmFPX serving
   kingjones777/Qwen3.8-27B-ROCmFPX-Q8_0-AGENT-GGUF; kept as the record of the