api-connectlisted

# api-connect - the API setup concierge ## Overview Takes over the work of connecting an external service's API/CLI to a project, so the user has to do as little as possible. The ideal: **all the user does is "log in" and "press the copy button and paste into .env"**. Research, navigating to the right screen, creating config files and the connectivity check are all done by the AI. **Principle: don't bombard them with questions.** Once you know the service name and the goal, confirm at most once and get moving. ## Iron rules (security) **Follow these literally. There is no "just this once".** 1. **Don't let secrets into the chat, and don't put them there yourself.** Never ask the user to paste an API key, token, secret or password into the chat. If the user pastes one by mistake, tell them immediately: "revoke that key and reissue it". 2. **The only hand-off mechanism is pasting directly into a .env file.** The AI creates the .env with placeholders first, and the user only has to hit the copy button in the admin console and paste it into the relevant line of .env. 3. **The AI does not log in, enter passwords, or create accounts.** Take them as far as the login page and have the user do it. The same goes for CAPTCHAs. 4. **Don't display .env values.** Load them entirely inside the shell, e.g. `set -a; . ./.env; set +a`, and never `cat .env` or echo a value. Check that the connectivity-check output contains no keys before showing it. 5. **Don't perform irrevers