[bobdivx]

Bug (prod 2.0.260)

An xAI key was pasted by mistake. Cursor refused it (worker.err: "The provided API key is invalid. The API key was loaded from the CURSOR_API_KEY environment variable.", which is the env var DevForge itself sets for the worker process). After that the tab gave no visible way to fix the key:

• the install/reinstall modal only showed the key field when no key was stored;
• the only replace field sat in « Avancé », whose tile said "Tout est rempli automatiquement";
• the server accepted the xai- key, and the tile only showed "Arrêté", not "clé refusée";
• there was no way to delete the key.

Fix

• The install modal always shows one masked "Clé API Cursor" field. The stored key appears only as a masked placeholder (never sent back), a typed value replaces it, and an empty field keeps it.
• key_invalid is detected from the worker logs. The tile shows "Clé KO" and the Avancé tile says "Clé API refusée : la remplacer". The modal shows an alert plus the required key field with a hint (cursor.com/dashboard → API Keys, not xAI). A failed install with a refused key offers "Réessayer avec cette clé".
• Avancé: replace the key, or delete it (with confirmation).
• Obvious non-Cursor keys (xai-, sk-, sk-ant-, sk-or-, gsk_, AIza, ghp_, gho_, github_pat_, hf_) are rejected client-side and server-side. Install refuses to restart with a stored foreign key and asks for a Cursor key.
• Precedence unchanged and explicit: a key saved in DevForge always wins over a server CURSOR_API_KEY. env_key_present (boolean only) lets the UI explain this.
• Changing the key clears the stopped worker's old logs, so the old error disappears.
• The key field uses autocomplete="new-password" so a password manager cannot fill the DevForge login password into it.

Tests

• Rust: foreign-key rejection, invalid-key log detection, hint.
• Web: cursorKeyProblem, and installNeeds / workerSummary with key_invalid.