docs+units: fix every claim my own changes made false

Retiring dankclaw/compose.yaml and adding alert rules invalidated claims across
the repo, including in the rule file agents read first. Clean cutover includes
the prose.

**Tests that had gone hollow.** Four assertions grepped dankclaw/compose.yaml
for a service name. With the file gone they passed by *absence* — a gate that
can no longer fail. Each now asserts the real invariant ("no dankclaw compose
file competes with the quadlet units") and keeps a live check for a re-added
entry, so it still fails when one appears: verified by recreating a compose file
with a comfyui service and watching three tests go red, then removing it.

**AGENTS.md, which was wrong about ComfyUI.** It said ComfyUI runs CPU-only
("no ROCm wheels for gfx1151, CUDA images wrong"). That was true in the
compose era and is false now: the restored unit runs with /dev/kfd + /dev/dri and
must NOT pass --cpu. An agent trusting the rule file would have re-broken it.
Also corrected: the observability paragraph ("RUNNING BUT UNCONFIGURED, no
datasource, no rules" — all three have been configured since 2026-09-16), the
Active runbook row that still named halogen for frank-large, halogen's absence
from the Retired table, the benchmark policy naming halogen's harness, and the
seam list.

**Unit and page claims.** prometheus.container said "no alerting rules anywhere
in this stack"; node-exporter.container said Dankserver runs from its compose
stack; Prometheus.md documented three jobs as working (they scrape HTML: they
can never report up) and said no dashboard existed; index.md and the three
authentik service pages pointed at the retired file; Authentik.md's upgrade
instruction told you to bump an image tag in it.

One bad edit of my own on the way (a stale line number clobbered a See Also
entry in Prometheus.md) — caught by reading back, fixed, and the vault link
checker now proves the cross-references hold.

tests/comfyui_rocm.bats

@@ -32,8 +32,12 @@ load helpers
     grep -q '^Image=localhost/comfyui-rocm:gfx1151$' "$unit" \
         || { echo "unit must run the locally built image"; return 1; }
     # One owner per container name: a surviving compose service would fight the
-    # unit for the container, which is how the stale one stayed alive.
-    ! grep -qE '^\s+comfyui:' "$REPO_ROOT/dankclaw/compose.yaml"
+    # unit for the container, which is how the stale one stayed alive. The file
+    # itself is retired (observability_quadlet.bats asserts that), so here the
+    # regression to catch is a re-added entry — the check must not go hollow
+    # just because the file is absent.
+    local cf="$REPO_ROOT/dankclaw/compose.yaml"
+    [ ! -f "$cf" ] || ! grep -qE '^\s+comfyui:' "$cf"
 }
 
 @test "comfyui Containerfile is based on the gfx1151 torch image" {