CiC TASK — ROTATE the OpenRouter API key (revoke leaked key + create new) — human-in-loop
Reason: the previous key (ends …c22b3e0) was exposed in plaintext; revoke it and mint a fresh one.

GROUND RULES
- Guided, human-in-the-loop. PAUSE for any login / OAuth / CAPTCHA / OTP.
- NEVER type my password. Do NOT read out or paste the new key anywhere — it shows once; I copy it myself.

STEPS
1. Go to https://openrouter.ai and ensure I'm logged in (PAUSE for me to log in if needed).
2. Open Keys: https://openrouter.ai/settings/keys
3. REVOKE THE OLD KEY FIRST:
   - Find the existing key (likely named "health-tracker-ocr", or the one ending …c22b3e0).
   - Click its delete/revoke (trash) control. CONFIRM deletion. Tell me it's revoked.
4. CREATE A NEW KEY:
   - Click "Create Key". Name it "health-tracker-ocr-2". Leave limits at default. Create.
   - HANDOFF: the new key (sk-or-...) shows ONCE. I will copy it now. Do NOT echo it.
     Wait for me to confirm "copied".
5. (If not already off) Settings -> Privacy: confirm "training and logging" is OFF.
6. CONFIRM to me: old key revoked = yes/no ; new key "health-tracker-ocr-2" created + copied = yes/no.
   Then STOP.

AFTER (owner): save the new key server-side WITHOUT it leaking. In a REAL SSH terminal
(not the Claude session, where the hidden prompt is masked correctly):
    cd /var/www/Others/health && ./save_key.sh
Paste the new key at the hidden prompt. Then tell Claude to reload + re-verify OCR.