RAILIANCE-WP-0002 T06 partial: DNS live for vergabe-teilnahme.whywhynot.de

A record now resolves to 92.205.130.254 (Traefik LB). HTTP probe
reaches Traefik and returns 404 as expected (no Ingress rule yet).
Ingress + cert-manager TLS will be created together with the backing
Service from T05 to avoid wasting a Let's Encrypt issuance attempt.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

workplans/railiance-apps-WP-0002-vergabe-teilnahme-on-railiance01.md

@@ -377,7 +377,7 @@ and produces no plaintext secrets in the rendered manifest source.
 
 ```task
 id: RAILIANCE-WP-0002-T06
-status: todo
+status: in_progress
 priority: high
 state_hub_task_id: "8e673ee6-5338-4eb5-8973-a1818b4dc7f5"
 ```
@@ -405,6 +405,17 @@ resource that consumes the existing controller.
 **Done when:** the public hostname serves the app over HTTPS and the
 certificate chain validates from outside the cluster.
 
+**Progress (2026-05-18):**
+
+- ✅ DNS A record live: `vergabe-teilnahme.whywhynot.de → 92.205.130.254`
+  (TTL 3600; served authoritatively by `ns1126.ui-dns.*`).
+- ✅ Traefik routing reaches the cluster: HTTP probe returns 404 — the
+  expected pre-state because no Ingress rule matches the host yet.
+- ⏳ `manifests/vergabe-teilnahme-ingress.yaml` — not yet created (waits
+  on T05's Service to point at; creating the ingress before the backend
+  Service exists would waste a Let's Encrypt issuance attempt).
+- ⏳ `vergabe-teilnahme-tls` Secret — pending ingress.
+
 ---
 
 ### T07 — Initial migration, seed, and smoke test