Claude Code: Always regenerate .env from .env.example on startup

Prevents split-brain state where uvicorn and worker process use different
environment contexts. Previously, .env was only created if missing, which
could cause stale configs when HF secrets change.

Co-Authored-By: Claude Code

entrypoint.sh

@@ -23,16 +23,15 @@ echo "=========================================="
 # Change to app directory
 cd /app
 
-# Ensure .env exists (create from .env.example if missing)
-# This ensures both uvicorn and worker share the same environment context
-if [ ! -f "/app/.env" ]; then
-    if [ -f "/app/.env.example" ]; then
-        echo "Creating .env from .env.example..."
-        cp /app/.env.example /app/.env
-    else
-        echo "WARNING: .env.example not found, creating empty .env..."
-        touch /app/.env
-    fi
+# CRITICAL: Always regenerate .env from .env.example before starting services
+# This prevents split-brain state where uvicorn/worker use different env contexts
+# when .env exists but is outdated (e.g., HF secrets changed in Space settings)
+if [ -f "/app/.env.example" ]; then
+    echo "Regenerating .env from .env.example (ensures fresh environment context)..."
+    cp /app/.env.example /app/.env
+else
+    echo "WARNING: .env.example not found, creating empty .env..."
+    touch /app/.env
 fi
 
 # Load .env file (for local development - ensures worker and uvicorn share env)