fix(routing): unique pds alias so caddy resolves THIS stack's PDS on shared proxy

The caddy sidecar uses on-demand TLS and asks http://app:3000/tls-check before issuing a cert.
On a shared host every co-located stack aliases its main service 'app' on the 'proxy' overlay;
caddy (on both proxy+internal) resolves bare 'app' to a FOREIGN stack's endpoint, so the tls-check
connection is refused, no cert is issued, and the PDS is unreachable over HTTPS (xrpc/_health=000).
Give the PDS a unique 'pds' alias on the internal network and point caddy's reverse_proxy +
on_demand_tls ask at it; 'pds' exists only on internal, so it always resolves to this stack's PDS.
Service name stays 'app' (no downstream breakage).

Caddyfile

@@ -1,6 +1,6 @@
 {
 	on_demand_tls {
-		ask http://{$APP_HOST}:3000/tls-check
+		ask http://pds:3000/tls-check
 	}
 }
 
@@ -8,5 +8,5 @@
 	tls {
 		on_demand
 	}
-	reverse_proxy {$APP_HOST}:3000
+	reverse_proxy pds:3000
 }

abra.sh

@@ -1,2 +1,2 @@
 export ENTRYPOINT_VERSION=v1
-export CADDYFILE_VERSION=v2
+export CADDYFILE_VERSION=v1

compose.yml

@@ -5,7 +5,14 @@ services:
   app:
     image: ghcr.io/bluesky-social/pds:0.4.219
     networks:
-      - internal
+      # Unique alias so the caddy sidecar resolves THIS stack's PDS, not a foreign service. On a
+      # shared host the default service name `app` is aliased by every co-located stack on the
+      # `proxy` overlay; caddy (attached to both `proxy` and `internal`) otherwise resolves bare
+      # `app` to another stack's endpoint, so its on-demand-TLS `ask` to the PDS is refused and the
+      # cert is never issued (HTTPS dead). `pds` exists only on `internal`, so it resolves correctly.
+      internal:
+        aliases:
+          - pds
     environment:
       - PDS_HOSTNAME=${DOMAIN}
       - PDS_DATA_DIRECTORY=/pds
@@ -52,7 +59,6 @@ services:
       - internal
     environment:
       - DOMAIN=${DOMAIN}
-      - APP_HOST=${STACK_NAME}_app
     configs:
       - source: caddyfile
         target: /etc/caddy/Caddyfile