chore(env): rotate GEMINI_API_KEY to the key that other Mana services use

Google returned `API_KEY_INVALID · API key expired` on the first
Wardrobe Nano Banana Try-On. The expired key (AIzaSyBR9iP74h...) had
been in .env.development for food image analysis and was carried over
to the new picture/generate-with-reference google/ branch.

Three other AIza keys live in the repo:
- AIzaSyCD50Yosl... — mana-llm/.env + .env.secrets (GOOGLE_API_KEY)
- AIzaSyC_-hPWpV... — .env.development PLANTA_GEMINI_API_KEY
- AIzaSyA0rTThrA... — .env.secrets + mana-research/.env + mana-auth/.env
                      (GOOGLE_GENAI_API_KEY), the one used by every
                      currently-running Gemini consumer.

Adopting the last one for GEMINI_API_KEY brings the whole monorepo
onto the same active credential. Probed `GET
/v1beta/models?key=…` against the new value → HTTP 200. `pnpm
setup:env` regenerated `apps/api/.env`; mana-api restarted to pick
up the fresh env.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

.env.development

@@ -248,8 +248,11 @@ FOOD_BACKEND_PORT=3023
 FOOD_DATABASE_URL=postgresql://mana:devpassword@localhost:5432/mana_platform
 FOOD_APP_ID=food
 
-# Google Gemini API for food image analysis
-GEMINI_API_KEY=AIzaSyBR9iP74hlo-mhI-Cl4QEvKprRzPPMb-GA
+# Google Gemini API — feeds food image analysis AND mana-api Wardrobe
+# Try-On (Nano Banana edits). Rotated 2026-04-24: previous key
+# AIzaSyBR9... expired with "API_KEY_INVALID / API key expired".
+# Matches GOOGLE_GENAI_API_KEY used by mana-research + mana-auth.
+GEMINI_API_KEY=AIzaSyA0rTThrAXgz1BLPqALeyMFG64GSgtu88A
 
 # S3 Storage (uses MinIO locally via shared S3_* variables)
 FOOD_S3_PUBLIC_URL=http://localhost:9000/food-storage