email.always and --no-email #115

Parent

#109

What to build

email.always = true in the User config makes every Run on the machine send a Run notification to email.to without the flag. no-email / --no-email skips it for one Run. With no email.always, a Run sends a notification only when --email is given.

If email.always is set and there is no email.to or no RESEND_API_KEY, the Run stops at the notification preflight, as with the flag. --email together with --no-email is an argument error (exit 2). Help and README document email.always and --no-email.

Acceptance criteria

• With email.always = true and email.to set, a Run without the flag sends one Run notification to email.to
• With email.always = true, --no-email and no-email each stop the notification, and the stand-in receives nothing
• With email.always = true, an address after --email still wins over email.to
• With email.always = true and no email.to, the Run stops at preflight naming the missing address
• With email.always unset or false, a Run without the flag sends nothing
• --email together with --no-email exits 2 with an error and the help text, before any work
• Help text and README document email.always and --no-email

Blocked by

• --email sends a Run notification whenever a Run ends #114