fix(streaming): bind trickplay to real data dir, not a phantom path

Jellyfin 10.11's data dir is /config/data/data, so trickplay resolves to
/config/data/data/trickplay. The bind targeted /config/data/trickplay, which
Docker happily created and Jellyfin never used -- 11G of trickplay tiles went
to the 194G root SSD instead of the ZFS array, with root at 84%.

Metadata is unaffected: MetadataPath is set independently and its bind at
/config/data/metadata is live.

Existing 11G rsynced to /storage1/labdata/jellyfin/trickplay; root 84% -> 78%.

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

stacks/streaming/docker-compose.yml

@@ -5,8 +5,11 @@
 # 194G and has filled twice; nothing here may grow unbounded on it.
 #
 # Jellyfin 10.11 (linuxserver) keeps metadata at /config/data/metadata — NOT
-# /config/metadata. Trickplay is at /config/data/trickplay and is not
-# relocatable from the UI. Transcodes are configured to /transcode.
+# /config/metadata. Trickplay is NOT a sibling of metadata: the server's data
+# dir is /config/data/data, so trickplay resolves to /config/data/data/trickplay.
+# Binding /config/data/trickplay silently does nothing and dumps trickplay tiles
+# on the 194G root SSD (found 2026-08-11 at 11G with root at 84%).
+# Transcodes are configured to /transcode.
 #
 # Transcodes are disk-backed, not tmpfs: jellyfin#16608 means Remux and
 # DirectStream jobs finish before the segment cleaner's first check, orphaning
@@ -33,7 +36,7 @@ services:
       - /config/jellyfin:/config
       - /storage1/labdata/jellyfin/metadata:/config/data/metadata
       - /storage1/labdata/jellyfin/cache:/config/cache
-      - /storage1/labdata/jellyfin/trickplay:/config/data/trickplay
+      - /storage1/labdata/jellyfin/trickplay:/config/data/data/trickplay
       - /storage1/labdata/jellyfin/transcodes:/transcode
       - /storage1/Movies:/data/movies:ro
       - /storage1/TV:/data/tv:ro