Self-host email: Settings, Emails, the install guide's email choice, and Admin, Self-host - #231

Summary

The dashboard and install guide side of opt-in email on self-hosted installs, CoderHelm's mail relay, and the platform admin's Self-host view. Pairs with CoderHelm/coderhelm-platform#315, which holds the inventory of every email, the relay and the threat model.

Changes

Settings, Emails (/settings/emails; self-hosted installs, install admins, capability emails)

• Lists the optional emails (weekly summary, welcome), each with a one-line description and an on/off switch. They are off on a new install.
• Send email: "Through my own Amazon SES", with the sender, the note that SES production access is needed and a link to the email setup check, or "Through Coderhelm (easiest)", with the plain statement of what CoderHelm sees. The CoderHelm option stays disabled until the install is registered for hybrid. Once chosen, the page shows whether the relay is working, paused, or not answering. Nothing falls back to SES.
• Lists the essential emails read-only, each with why it is needed.
• The Setup checklist gains an optional item, "Optional emails chosen".

Admin, Self-host (/admin/self-host; platform admins only, a second page of the Admin section)

• The summary at the top covers installs (total, active in 7 days, revoked), CoderHelm addresses claimed and live, the GitHub relay (linked installations, events in 24 hours and 7 days, failure rate), the token broker, each integration app, the email relay (opted in, sent, bounce and complaint rates, paused, recipient count) and installs that share delivery data.
• A 7-day chart of relay events and emails.
• A table of installs: name and address, version, registered, last seen, the parts that are on, events and emails in 7 days, and status. Each row opens its numbers, its audit log, and Pause email or Resume email and Revoke.
• Metadata only. Recipients appear only as counts.

Install guide (docs/components/install/wizard.tsx, docs/lib/install/core.ts)

• Send email is now a choice: "Send email through CoderHelm (easiest)", with its one-line trust note, or "Through my own Amazon SES". Neither is preselected. Left unpicked, the install uses its own SES until an admin picks in Settings, and the page says so.
• The From field shows only for the SES option, with its confirm-link explanation.
• Choosing CoderHelm passes EmailTransport=coderhelm to the Launch Stack and registers the install for hybrid.
• One line: "Optional emails such as the weekly summary start off; turn them on in Settings, Emails."
• Optional setup gains "Weekly summary email (off; turn on in Settings)". With CoderHelm chosen, the SES item is hidden.

Verification

• Dashboard: tsc --noEmit and npm run lint (UI lint) pass.
• New e2e/emails.spec.ts (6 tests): optional emails start off, essential emails read-only, a switch saves, choosing the relay, the relay needs registration, non-admins redirected, Admin Self-host totals, trend, rows, detail with audit log, pause, no addresses on the page, refused for non-admins. Screenshots at 1440 and 390, reviewed.
• Dashboard e2e on the specs this touches (emails, selfhost, settings-pages, settings, admin, no-sideways-scroll, shell-menu, layout): 184 pass. Two fail: selfhost.spec.ts "Setup: failing checks... Check again" at 1440 and 390 (checksState.runs is 3, not 2). That test fails the same way on main without this change.
• Docs: npm run build against the paired platform branch, check:links, unit tests (82 pass, including the email choice in the quick-create link and in Optional setup) and the full e2e suite (135 pass). Screenshots at 1440 and 390 reviewed.
• Rebased on main (Talk to us about moving from CoderHelm cloud to self-host #225, Docs: tables that read on a phone, and settings as definition lists #226, Settings, System, Models: switch how a self-hosted install calls Claude, and show when an update needs model access #230).
• The name grep is empty. No arrow glyphs. No AWS writes.