fix(infra): sablier-support must be no-op until traefik wiring is ready

Copying the sablier-encryptid.yml labels would immediately apply
traefik.enable=false to the live encryptid container, breaking auth
before Sablier has a middleware route in place. Reduced to empty
services:{} with a comment explaining what's needed to activate.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

docker-compose.sablier-support.yml

@@ -1,10 +1,13 @@
-services:
+# Sablier override — referenced by COMPOSE_FILE on Netcup.
-  encryptid:
+#
-    labels:
+# Currently a NO-OP placeholder so `docker compose` commands don't fail when
-      - "sablier.enable=true"
+# COMPOSE_FILE includes this path. Real Sablier activation is deferred until
-      - "sablier.group=encryptid"
+# Traefik middleware wiring is ready — see docker-compose.sablier-encryptid.yml
-      - "traefik.enable=false"
+# for the encryptid label pattern, which cannot be applied in place because
-  encryptid-db:
+# `traefik.enable=false` on the encryptid container would immediately break
-    labels:
+# auth traffic without a Sablier-backed route in front of it.
-      - "sablier.enable=true"
+#
-      - "sablier.group=encryptid"
+# To activate: add sablier labels here AND configure Traefik dynamic config
+# to route encryptid's hostname through the Sablier middleware.
+
+services: {}