@reddoorla/maintenance 0.10.0 → 0.10.1

package/README.md

@@ -314,7 +314,60 @@ RESEND_WEBHOOK_SECRET=whsec_XXXX  # only for the deployed webhook
 
    Renders + sends every Reports row with `Draft ready=true && Approved to send=true && Sent at IS NULL`. Stamps `Sent at` + `Delivery status=pending` on each.
 
-5. **Delivery status updates automatically** via the Resend webhook (Netlify Function at `netlify/functions/resend-webhook.mts`) — `Delivery status` flips to `delivered` / `bounced` / `complained` as events arrive.
+5. **Delivery status updates automatically** via the Resend webhook (Netlify Function at `netlify/functions/resend-webhook.mts`) — `Delivery status` flips to `delivered` / `bounced` / `complained` as events arrive. Deploy procedure: see [Webhook deployment](#webhook-deployment-netlify--resend) below.
+
+### Webhook deployment (Netlify + Resend)
+
+The Resend delivery webhook lives at `netlify/functions/resend-webhook.mts` in this repo. Deploying it is a one-time operation per environment: connect the repo to a Netlify site, set three env vars, register the deployed URL with Resend.
+
+**1. Create the Netlify site:**
+
+- New site → Import from Git → pick `tucksravin/reddoor-maintenance`.
+- Branch to deploy: `main`. Build settings are read from [`netlify.toml`](netlify.toml) (no build command needed — functions-only).
+- Site name: pick something stable (e.g. `reddoor-webhooks`) since it ends up in the public webhook URL.
+
+**2. Set env vars** in Site settings → Environment variables:
+
+| Variable                | Value                                                                       |
+| ----------------------- | --------------------------------------------------------------------------- |
+| `AIRTABLE_PAT`          | Same PAT used by the CLI (read+write on the Websites + Reports tables)      |
+| `AIRTABLE_BASE_ID`      | `appHG8nLOzULzXOER`                                                         |
+| `RESEND_WEBHOOK_SECRET` | Generated by Resend in step 4 — paste back here after creating the endpoint |
+
+**3. Trigger a deploy** (Deploys → Trigger deploy → Deploy site). When it goes green, curl the health endpoint:
+
+```bash
+curl https://<your-site>.netlify.app/.netlify/functions/resend-webhook
+```
+
+Expected:
+
+```json
+{
+  "status": "ok",
+  "service": "reddoor-resend-webhook",
+  "env": {
+    "RESEND_WEBHOOK_SECRET": true,
+    "AIRTABLE_PAT": true,
+    "AIRTABLE_BASE_ID": true
+  }
+}
+```
+
+Any `false` means the env var didn't land — re-check step 2 and re-deploy. The health endpoint reports presence-only and never returns secret values, so the output is safe to share in a support ticket.
+
+**4. Register the webhook in Resend:** [resend.com/webhooks](https://resend.com/webhooks) → Add Endpoint → paste the function URL from step 3 → select events `email.delivered`, `email.bounced`, `email.complained` → save. Copy the generated **Signing Secret** (`whsec_…`) into Netlify's `RESEND_WEBHOOK_SECRET` env var (step 2) and trigger another deploy so the secret takes effect.
+
+**5. End-to-end smoke test (using ERP Industrials):**
+
+```bash
+# from your CLI:
+reddoor-maint report erp-industrials   # drafts a Maintenance report → Airtable
+# approve the draft in Airtable, then:
+reddoor-maint report --send-ready
+```
+
+Within a few minutes, watch the ERP Reports row's `Delivery status` flip from `pending` → `delivered` as Resend pings the webhook. Function logs in Netlify show each event with its messageId + new status. If the webhook returns 5xx, svix retries; check the Netlify function log for the error envelope.
 
 ### Frequency math
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reddoorla/maintenance",
-  "version": "0.10.0",
+  "version": "0.10.1",
   "description": "Canonical maintenance configs, audits, and recipes for the reddoor stack.",
   "type": "module",
   "license": "MIT",