fix(deploy): mount the Bot API directory with the long volume syntax

A bot token contains a colon and the path to mount contains the token, so
Compose's "source:target" form counted three colons and refused:
"invalid spec: ... too many colons". CI caught it in validation; it would
have failed the same way on the host.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014xA348oKfgDBSH1mbUkej3

Author: amtiYo

CHANGELOG.md

@@ -46,7 +46,9 @@ GitHub Releases.
 ### Operations
 
 - The WS04 stack mounts `<bot api data>/<token>` and runs as uid 101, the user
-  the Bot API server writes as. Files are removed after transcription, which a
+  the Bot API server writes as. The mount uses Compose's long volume syntax:
+  the path contains the token, the token contains a colon, and `source:target`
+  splits on colons. Files are removed after transcription, which a
   local server never does on its own.
 
 ## v0.0.1-beta.1 - 2026-09-06

deploy/ws04/compose.yaml

@@ -21,8 +21,12 @@ services:
     # directory has to be mounted — but only this bot's own subdirectory. The
     # parent holds one subdirectory per bot, each named after that bot's full
     # token, and mounting it would hand Voicy every other bot's credentials.
+    # Long syntax, not "source:target": a bot token contains a colon, and the
+    # short form splits on colons.
     volumes:
-      - ${BOT_API_HOST_DIR:-/opt/stacks/telegram-bot-api/data}/${TELEGRAM_BOT_TOKEN:?TELEGRAM_BOT_TOKEN must be set for the Bot API files mount}:/var/lib/telegram-bot-api/${TELEGRAM_BOT_TOKEN}
+      - type: bind
+        source: ${BOT_API_HOST_DIR:-/opt/stacks/telegram-bot-api/data}/${TELEGRAM_BOT_TOKEN:?TELEGRAM_BOT_TOKEN must be set for the Bot API files mount}
+        target: /var/lib/telegram-bot-api/${TELEGRAM_BOT_TOKEN}
     # The Bot API server writes as uid 101 with mode 0750. Voicy has to read
     # those files and delete them afterwards, because a local server never
     # reclaims what it produced.