docs(protocols): surface cmail-action send as the default email path

An org-drill session asked to send a follow-up email first claimed it couldn't, then hand-built MIME through msmtp, because nothing told it cmail send exists. I added a "Sending Email" subsection to protocols.org (read every session): cmail (c@cjennings.net) is the default for personal mail, dmail for work, and cmail-action send is the tool, with one-liner examples for body-file, attachments, Cc/Bcc, and threaded replies. I also rewrote send-email.org Step 4, replacing the inline-Python heredoc that taught the hard way with the cmail-action send call.

1 files changed, 26 insertions, 0 deletions

diff --git a/.ai/protocols.org b/.ai/protocols.org
index d5290aa..1499fbb 100644
--- a/.ai/protocols.org
+++ b/.ai/protocols.org
@@ -261,6 +261,32 @@ for it on a specific document* — never sign for him on your own initiative. Th
 =edit-pdf= workflow (project-level, where present) has the reportlab snippet for
 stamping it.
 
+** Sending Email
+
+Craig has three mail accounts. *Default to cmail for personal / non-work email* — reach for it unless the message is work-related.
+
+| Account | Address | Use for |
+|---------+---------+---------|
+| =cmail= | =c@cjennings.net= (Proton Bridge) | *Default.* Personal / non-work mail. |
+| =dmail= | =craig.jennings@deepsat.com= (Gmail) | Work mail. |
+| =gmail= | =craigmartinjennings@gmail.com= | Third account, rarely the right one. |
+
+*The tool is =cmail-action send=* (symlinked into =~/.local/bin=, on PATH from any project). Don't hand-roll MIME or pipe raw messages through =msmtp= — the script builds the message, threading, and attachments for you.
+
+#+begin_src bash
+# simple
+cmail-action send --to addr@example.com --subject "Subject" --body "One-liner body."
+# body from a file (preferred for anything multi-line)
+cmail-action send --to addr@example.com --subject "Subject" --body-file /tmp/draft.txt
+# with attachments (repeatable --attach, MIME type auto-detected)
+cmail-action send --to addr@example.com --subject "Subj" --body-file /tmp/draft.txt --attach a.pdf --attach b.png
+# a threaded reply
+cmail-action send --to addr@example.com --subject "Re: ..." --body-file /tmp/draft.txt \
+  --cc someone@example.com --in-reply-to "<msgid>" --references "<msgid>"
+#+end_src
+
+=cmail-action= handles the receive/triage side too (=list-unread=, =read=, =mark-read=, =star=, =trash=). For the full guided flow (validate the recipient against =contacts.org=, confirm before sending, verify delivery), run the =send-email= workflow; for a known recipient, the one-liner above is enough.
+
 ** Task List Location
 Craig's global task list is available at: =/home/cjennings/sync/org/roam/inbox.org=