fix(ci): disable LFS fetch (budget exhausted); wire Google Maps key into build

- CI checkout no longer pulls the 254MB flood model via LFS; the repo's
  LFS bandwidth budget is exceeded and tests use the synthetic/demo
  fallback exactly like production does
- Dockerfile accepts VITE_GOOGLE_MAPS_API_KEY as a build arg so the Vite
  build bakes in the Maps browser key, enabling the region picker
- deploy workflow forwards the key from repo secrets

Author: Goldokpa

.github/workflows/ci.yml

@@ -14,7 +14,10 @@ jobs:
     steps:
       - uses: actions/checkout@v7
         with:
-          lfs: true
+          # LFS disabled: the repo's LFS bandwidth budget is exhausted and the
+          # 254MB flood model isn't needed for tests (code falls back to the
+          # synthetic/demo model path, same as production).
+          lfs: false
 
       - name: Set up Python
         uses: actions/setup-python@v6

.github/workflows/deploy.yml

@@ -43,7 +43,10 @@ jobs:
       - name: Deploy to Fly.io
         env:
           FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}
-        run: flyctl deploy --remote-only --ha=false --wait-timeout 600
+          VITE_GOOGLE_MAPS_API_KEY: ${{ secrets.VITE_GOOGLE_MAPS_API_KEY }}
+        run: >-
+          flyctl deploy --remote-only --ha=false --wait-timeout 600
+          --build-arg VITE_GOOGLE_MAPS_API_KEY="$VITE_GOOGLE_MAPS_API_KEY"
 
       - name: Show status
         env:

Dockerfile

@@ -13,6 +13,9 @@ RUN npm ci
 
 COPY frontend/ ./
 ENV VITE_API_BASE_URL=
+# Google Maps browser key is baked in at build time (Vite inlines import.meta.env).
+ARG VITE_GOOGLE_MAPS_API_KEY=
+ENV VITE_GOOGLE_MAPS_API_KEY=$VITE_GOOGLE_MAPS_API_KEY
 RUN npm run build
 
 # -----------------------------------------------------------------------------