trails/openspec/changes/archive/2026-03-26-transactional-emails/proposal.md
Ullrich Schäfer ba044610b7
Add route interactions: click-to-split, drag-to-reshape, colored route rendering
- Enrich BRouter response with per-point 3D coordinates and segment boundary
  tracking (EnrichedRoute interface)
- ColoredRoute component: plain, elevation gradient (green→yellow→red), and
  surface color modes with invisible wide polyline for click targeting
- Click-to-split: click on route polyline inserts waypoint at nearest point,
  mapped to correct segment via boundary indices
- MidpointHandles: draggable CircleMarkers at route segment midpoints for
  reshaping, hidden below zoom 12, opaque on hover
- Color mode toggle (select) synced via Yjs routeData
- i18n keys for color mode labels (en + de)
- Unit tests for segment boundary tracking (13 tests)
- E2E tests for enriched route response and color mode toggle

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-26 22:36:42 +01:00

1.3 KiB

Why

Magic link login doesn't work in production — the link is logged to console but never emailed to the user. Registration works (passkey-based) but the fallback auth flow is broken. We need actual email delivery.

What Changes

  • Add a reusable email sending layer (@trails-cool/email or in-app module) with a provider-agnostic interface so future emails are trivial to add
  • Send magic link emails in production
  • Send a welcome email after registration
  • Use a transactional email provider (Resend, Postmark, or SMTP)
  • HTML email templates with plain-text fallback
  • Document email sending in the privacy manifest

Capabilities

New Capabilities

  • transactional-emails: Send templated emails via a provider-agnostic interface. Current emails: magic link login, welcome on registration. Designed for easy addition of future email types.

Modified Capabilities

  • journal-auth: Magic link flow now actually sends the email instead of logging to console

Impact

  • Files: New email module (lib or package), modified api.auth.login.ts, modified registration flow, email templates
  • Dependencies: One email provider SDK (e.g., resend or nodemailer)
  • Infrastructure: Email provider API key as env var, DNS records for sender domain verification
  • Privacy: Email addresses sent to third-party email provider — must document