fix: stop old containers before compose up in production deploy

- Add docker compose down step before up to ensure the production
  container is recreated with the freshly-built image
- Without this, compose sees the old running container and skips it,
  while the Docker 24 network bug is silently swallowed by || true

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

.gitea/workflows/deploy.yml

@@ -244,6 +244,11 @@ jobs:
           set -e
           export DOCKER_API_VERSION=1.43
 
+          # Stop and remove old containers to force recreate with new image.
+          # External networks (gitea_gitea, nas-dashboard_internal) are preserved.
+          docker compose -f /nas-dashboard/docker-compose.yml down 2>/dev/null || true
+          echo "Old containers stopped"
+
           # Docker 24 compose fails when it can't connect external networks
           # during container creation. Try compose first; if the container
           # isn't created, strip networks from compose file and retry.