Agent setup

Set up HookMyApp for me. Follow these steps:

1. Check prerequisites. You need Node.js 20 or newer (npm ships with it):
   node -v
   If node is missing or below v20, STOP and tell me to install the current LTS from https://nodejs.org, then re-run.

2. Install the HookMyApp agent skills globally so this and future agent sessions know how to finish or recover the setup:
   npx skills add hookmyapp/agent-skills --all --global
   If the command fails, continue with the steps below because they contain the full setup flow. Tell me to run the skills command once manually afterward.

3. Install the HookMyApp CLI. Run this even if hookmyapp is already installed, so it upgrades to the latest version:
   npm install -g @gethookmyapp/cli

4. Sign me in. This also creates my free HookMyApp account if I don't have one yet. Look for email addresses that are likely mine (git config user.email, prior context). If you found any, ask me: "Your free HookMyApp account needs an email address. Should I use <the email(s) you found>, or a different one?" If you found none, ask me: "To set up your free HookMyApp account I need an email address. Which one should I use?" Either way, keep it to that one question, with no commands and no mention of where you looked. Once I confirm, run:
   hookmyapp login --email <my email> --json
   Run that initiation command exactly once. Save its registrationId and do not request another code. A 6-digit code is sent to my email. Tell me: "I just sent a 6-digit sign-in code to <email>. Paste it here so I can finish setting up your HookMyApp account." Any unexpired code sent to that same email during this 10-minute login window is valid. Complete with:
   hookmyapp login --email <my email> --registration-id <the saved registrationId> --otp <the 6-digit code> --json
   Use the hookmyapp CLI for everything until the MCP tools are live (see the HookMyApp skill).

5. Set yourself up to use HookMyApp directly:
   hookmyapp agent setup --no-skills
   This configures the HookMyApp MCP server in every coding agent installed on this machine. Read what it prints: it names the sign-in each one still needs. If it lists Codex, run:
   codex mcp login hookmyapp
   Do not try to prove this worked by calling a HookMyApp MCP tool now. You loaded your MCP servers when this session started, so any hookmyapp tool you can see is the old configuration and calling it proves nothing. Tell me to restart you instead.

6. Confirm the setup:
   hookmyapp doctor
   If doctor reports an error or exits non-zero, STOP and tell me what failed.

7. Set my alert phone so HookMyApp can reach me when the integration breaks later:
   hookmyapp alerts phone status
   If that already shows a verified number, skip this step. Otherwise tell me why before asking: HookMyApp texts this number (WhatsApp or SMS) when my webhooks start failing, a channel disconnects, or my plan limit is reached, so I find out even when I am not watching the logs. Then ask me for the number and run:
   hookmyapp alerts phone set <the number I give you>
   hookmyapp alerts phone verify <the 6-digit code I read back to you>
   Never invent the number or the code; both come from me. If I decline, skip it and continue; nothing downstream depends on it.

   Only after doctor succeeds, tell me setup is done. Also tell me to restart you, which is what makes the HookMyApp MCP tools available. The CLI already covers everything in the meantime.

If anything fails, STOP, preserve the registrationId, and tell me the exact error. Do not run the initiation command again or request another code unless all existing codes are expired or locked and I explicitly approve another email.