A skipped Architect run sends no Run notification #325

Parent

#311

What to build

A skipped Architect run sends no Run notification, for any reason it was skipped (another run still going, an open Architect plan, and any skip added later), and whether the email was asked for by the email flag or by email.always. That lets a crontab line fire every few minutes for Weeding without flooding the inbox. The skip still exits 0, and the command log keeps its line. The notification checks (an address and a Resend API key) still run first on every pass that asked for an email, so a broken setup fails the pass with exit 1 before the skip check, as today.

An Architect run that did work (plan published, idea filed, idea already filed, review failed, or a dispatched run that ended) still sends exactly one notification when asked.

Acceptance criteria

• An Architect run skipped as already running sends no email with email.always = true or with email on the line, and exits 0.
• An Architect run skipped for an open Architect plan sends no email, still exits 0, and still prints each plan's URL on stdout.
• A broken notification setup still fails a pass that would have been skipped, before the skip.
• The existing tests asserting that a skipped Architect run sends one notification (the "skipped in its subject" test and the "skipped for open plans … naming each" test) are rewritten to assert that none is sent.
• The README's Architect run notification and "On a schedule" text no longer promise an email on a skipped night, and say that the log holds the skip's line.
• ADR 0009's Consequences no longer say a skipped Architect run sends a notification.

Blocked by

None (can start immediately)