docs(vault): era-correct the vLLM/Ling era pages (cluster C3)

- `Running Qwen3.6 27B FP8 on Dankclaw`: had no banner at all and opened as a
  live how-to. Added the RETIRED banner (iGPU endpoint today is
  [[frank-dragoon]]), era-tagged the hardware table, and rewrote the
  "primary service now runs vLLM-ROCm with Ling CIRU INT4" production note,
  which was false by three fleet generations.
- `ling-3.0-flash-vllm-plan`: "frank-dragoon is the Qwen3.8-27B PP head" ->
  past tense with the 2026-08-17 redo as the anchor and the live owner named.
- `frank-redo-2026-08-17` banner: stripped restated live shapes that had
  already drifted (radiance 1.0.13, PrismML b10754 - the fleet runs 10777)
  and the 3090-provenance clause owned by the PP deployment page; banner is
  now locator-only (names + ports + links).

Verified before cutting: 457.9 t/s and the ping-RTT figures are solo-held by
Ethernet Bandwidth Math.md (no duplicate), so both scout-reported "duplicates"
were kept.

Refs: vault de-dup campaign, cluster C3.

serverAppConfigs-docs/LLM/ling-3.0-flash-vllm-plan.md

@@ -15,6 +15,8 @@ This page was the plan for a vLLM-ROCm deployment of
 Dankclaw. The deployment never shipped. The actual Ling work used the
 llama.cpp Q6_K fork trial instead: [[ling-3.0-flash-trial]].
 
-The trial service (`frank-dragoon-ling`) is retired and disabled under the
-boot policy (2026-08-17). `frank-dragoon` is the Qwen3.8-27B PP
-head, not the Ling path. See git history for the full decision table.
+The trial service (`frank-dragoon-ling`) was retired and disabled under the boot
+policy on 2026-08-17, in the same redo that renamed `frank-dragoon` to the
+Qwen3.8-27B PP head ([[frank-redo-2026-08-17]]). Two fleet generations later the
+name belongs to the halogen flash-server endpoint ([[frank-dragoon]]). See git
+history for the full decision table.