setup-email-updateslisted

# Bridge: Setup Email Updates **Announce at start:** "I'm using the bridge:setup-email-updates skill to configure who receives update emails for this repo." ## Purpose Both `send-update-email` and `send-update-email-batch` refuse to run against a repo that has no `.bridge/email-config.json`. This skill is the only thing that creates or edits that file — recipients, the `lastSentSha` tracking marker, and (on first setup) a dedicated per-repo Resend MCP connection so each repo can send under its own sender name. ## Requirements - `RESEND_API_KEY` environment variable, set wherever *this skill* runs (only needed at setup time — see Step 3). `send-update-email` itself never needs this variable; by the time it runs, the key already lives inside the per-repo MCP server this skill registers. ## Step 1 — Detect Mode ```bash git rev-parse --is-inside-work-tree 2>/dev/null ``` - Prints `true` → **single-repo mode**: go to Step 2. - Errors (not a git repo) → **batch mode**: go to Step 5. ## Step 2 — Single-repo: Check Existing Config ```bash test -f .bridge/email-config.json && cat .bridge/email-config.json || echo "NO_CONFIG" ``` - Prints `NO_CONFIG` → go to Step 3 (create). - Prints JSON → go to Step 4 (edit). ## Step 3 — Single-repo: Create Config Ask the user for: 1. The recipient email addresses (they can list as many as they want). 2. The sender "from" string to use for this repo's emails, e.g. `Bridge Bot (FlightPath) <noreply@yourdomain.com>`. Suggest a default of `