Storage: configurable data dir for the external drive + daily DB prune

HOST_DATA_DIR in .env can now point /data at a host path (the 1TB
external drive) instead of the named volume, so odds history, caches
and snapshots stop eating the 128GB root disk. A daily prune drops
cache entries stale for over a week and ingest-log rows older than 14
days — faster polling no longer means unbounded DB growth.

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

deploy/cup26.compose.yml

@@ -21,7 +21,11 @@ services:
       - ENABLE_SOFASCORE=${ENABLE_SOFASCORE:-false}
       - ENABLE_FOTMOB=${ENABLE_FOTMOB:-false}
     volumes:
-      - cup26-data:/data
+      # HOST_DATA_DIR (in .env) may point at a host path — e.g. the external
+      # 1TB drive — so the growing SQLite DB stays off the small root disk.
+      # An absolute path = bind mount; unset = the original named volume.
+      # The container runs as node (uid 1000): chown 1000:1000 the host dir.
+      - ${HOST_DATA_DIR:-cup26-data}:/data
     security_opt:
       - no-new-privileges:true
     mem_limit: 384m