send-email

name	send-email
description	Create a draft or send a Buttondown email for a specific newsletter, optionally starting from a local template. Confirms before any send — sends are not reversible.

Send Email

Steps

1. Pick newsletter. If named, resolve slug against config.json. Otherwise use default; if no default and multiple configured, ask.
2. Source. One of:
   • Path to a markdown file (default location: <newsletter.user_dir>/drafts/)
   • A template name from $DATA_ROOT/templates/ (filtered to scope: global or matching the chosen newsletter slug). If templated, prompt for any {{placeholders}} in the subject and body and substitute before showing the preview.
3. Docs lookup. Run docs-lookup for the create-email endpoint and publish/send semantics. Confirm current required fields (subject, body, status values like draft / scheduled / about_to_send).
4. Show resolved payload — newsletter, subject, body preview (first 30 lines), audience/segments, scheduled time if any.
5. Confirm before send. Status draft proceeds. Statuses that imply an actual send require explicit user confirmation in this turn — don't assume prior approval covers a new send. Sends fan out to subscribers and cannot be unsent.
6. Call the API with the API key resolved from the chosen newsletter's api_key_ref.
7. Archive. Write the request payload + response to <newsletter.user_dir>/sent/<date>-<slug>.json. If the email originated from a template, include the template name in the archive metadata.