build(deploy)!: compose.yaml's link goes, now learn.halkyon.eu's .env names compose.learn.yaml

The link carried the deploy that switched the server's COMPOSE_FILE over (2 Nov 2026).

BREAKING CHANGE: an instance whose deploy/.env still names compose.yaml, or sets no
COMPOSE_FILE, must name compose.learn.yaml first.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>

deploy/compose.learn.yaml

@@ -6,8 +6,7 @@
 #   docker compose up -d --build
 #
 # This file was compose.yaml until 2 Nov 2026, so .env's COMPOSE_FILE names it (Compose
-# finds no file by itself). compose.yaml is a link to it for the one deploy that
-# switches learn.halkyon.eu's .env over, and goes with the next commit touching deploy/.
+# finds no file by itself).
 #
 # Only Caddy publishes ports. Docker opens published ports directly in the kernel's
 # packet filter, past ufw, and the Serverpod server listens on every interface, so the

deploy/compose.yaml

@@ -1 +0,0 @@
-compose.learn.yaml