email-ops

Read the existing thread first to identify the last outbound touch, open commitments, and unanswered questions, then draft the reply using the correct sender account. For live sends, verify the final body, send through the mail surface, and confirm the message landed in Sent.

Verify a send by checking the Sent folder or an equivalent sent-copy store for the exact message. Never claim a message was sent based on the send action alone; report the state as sent only with Sent proof or explicit client-side confirmation.

Triage by archiving low-signal mail while explicitly preserving uncertain business correspondence rather than deleting it. Resolve the mailbox account and scope first, then report each action with exact status words like archived or blocked.

Use email when the task involves mailbox surfaces, threads, and Sent-folder verification; hand off to a messages-focused workflow when the task is really DM or iMessage work. Mixing the two leads to contextless replies and unverifiable send claims.

When the send surface is blocked, the draft is preserved and the exact blocker is reported instead of silently switching to a second transport. The final state is reported as blocked or awaiting verification with the reason stated.