Promote DC9 HAProxy front door to TCP 443

servers/bwh-us-dc9/frontdoor/.env.example

@@ -1,3 +1,2 @@
-# Stage on 8444 first. Change to 443 only after the Arcane Agent Caddy is
+# HAProxy owns public TCP 443. Hysteria2 owns public UDP 443 separately.
-# reachable through its temporary management port and host TCP 443 is free.
+HAPROXY_PUBLIC_PORT=443
-HAPROXY_PUBLIC_PORT=8444

servers/bwh-us-dc9/frontdoor/README.md

@@ -7,6 +7,6 @@ HAProxy inspects TCP SNI without terminating TLS:
 - `dc9.kais.cloud` -> the existing Arcane Agent Caddy on `arcane_default`
 - unmatched SNI -> the dedicated Caddy fallback serving `dc9.opfo.xyz`
 
-The first deployment uses host TCP 8444. Moving it to TCP 443 requires a staged
+HAProxy publishes host TCP 443. The existing Arcane Agent Caddy remains attached
-handoff from the existing Arcane Agent Caddy so the Direct HTTPS management path
+to `arcane_default` without a host TCP 443 binding and receives
-remains reachable throughout the change.
+`dc9.kais.cloud` traffic from HAProxy.

servers/bwh-us-dc9/frontdoor/compose.yaml

@@ -4,7 +4,7 @@ services:
     container_name: dc9-haproxy
     restart: unless-stopped
     ports:
-      - "${HAPROXY_PUBLIC_PORT:-8444}:8443/tcp"
+      - "${HAPROXY_PUBLIC_PORT:-443}:8443/tcp"
     extra_hosts:
       - "host.docker.internal:host-gateway"
     depends_on: