chore: add proxy-network compose for reverse-proxy deploys

docker-compose.proxy.yml runs the container on a shared external 'proxy'
network with no published ports, for hosting behind an existing edge
proxy (Caddy/Traefik/etc.) that routes <sub>.domain -> the-director:80.
This is how it's deployed at apps.timevans.uk.

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

docker-compose.proxy.yml

@@ -0,0 +1,14 @@
+# Deploy behind an existing reverse proxy (e.g. Caddy) that owns 80/443 on a
+# shared external docker network named "proxy". The container publishes no host
+# ports; the edge proxy routes to it by name: `reverse_proxy the-director:80`.
+#   docker compose -f docker-compose.proxy.yml up -d --build
+services:
+  director:
+    build: .
+    image: the-director:latest
+    container_name: the-director
+    restart: unless-stopped
+    networks: [proxy]
+networks:
+  proxy:
+    external: true