Changelog

Who edited what email, and why. The curated log below is the story (appended on every edit per the email playbook); the git feed underneath is the raw record, automatic from commits touching email files.

Curated — what changed & why (14)

• newPayment receiptclaude-aa2026-06-17
  Built Wave 2+3: payment receipt + payment failed (member billing), placement 30-day check-in, partner QBR invite, testimonial request (dual)
  Why Completes the recommended Tier-2: billing trust + the highest-leverage relationship moments
• newData export readyclaude-aa2026-06-17
  Built the compliance/security floor: 11 account/security emails (GDPR data-export/deletion/consent, email-change confirm+alert, MFA enabled/disabled, passkey added/removed, recovery-code-used) + partner-new-applicant (closes the candidate_submitted_to_partner unmapped-event bug)
  Why Tier-1 floor: the legal/security confirmations whose backends are already live, plus a broken partner path
• newReferences requestclaude-aa2026-06-17
  Built 4 net-new Tier-1 emails: references-request, candidate weekly + re-engagement digests, partner onboarding nudge, admin weekly exec summary
  Why Owner-approved net-new round; widens coverage across all three audiences
• auditJob matchesclaude-aa2026-06-17
  Audited the 6 Phase-D candidate bodies to ≥98
  Why Added purpose anchors (starting-soon, results), a strategist quote (assessment-invite), a preview fallback (message), and a zero-match guard (job-matches)
• auditDaily Ops Digest (platform)claude-aa2026-06-17
  Audited the 14 admin ops + digest bodies to ≥98
  Why Added ops-purpose closes, empty/zero-data guards, AI-insight empty-string guard, and churn/data-quality intelligence depth
• auditOffer declinedclaude-aa2026-06-17
  Audited the 22 concierge mirror + SLA bodies to ≥98
  Why Born-90 ops set converged: verified the six-lens spine (purpose + match% already woven in), set scores
• newFirst day prepclaude-aa2026-06-17
  Built first-day-prep onboarding email (logistics RoleCard + prep WhyList + calendar + strategist quote)
  Why Closed the one real coverage gap — the send-first-day-prep event had no body
• toolingatlasclaude-aa2026-06-17
  Added this changelog + the Atlas-sync ritual to the email AGENTS.md
  Why Keep the Atlas current on every edit and build a who/what/why history we can learn from
• toolingatlasclaude-aa2026-06-17
  Added search/filter, status chips, board device toggle, skip-link + landmarks + aria-pressed, and a per-email audit-basis line
  Why Make the overview clear, filterable, and accessible
• fixInterview scheduledclaude-aa2026-06-17
  PII-free partner-pipeline renders (demo personas, monogram avatars) via render-partner-pipeline.ts
  Why The hosted Atlas must never expose real candidate names or avatars
• toolingatlasclaude-aa2026-06-17
  Added component gallery (28), token reference, chrome map link, and the contribution guide
  Why Document the design system itself, not just the email outputs
• toolingatlasclaude-aa2026-06-17
  Added spec pages: render + metadata + view/copy/download HTML source + notes + open-GitHub-issue
  Why Give collaborators a Litmus-ready handoff and a place to leave feedback per email
• toolingatlasclaude-aa2026-06-17
  Added the per-email metadata spine in email-catalog.ts (audience/mail-class/sender/recipients/trigger/builder/status) + a RECIPIENT_MAP cross-check test
  Why Every surface reads one source of truth so the Atlas can't drift from the code
• toolingatlasclaude-aa2026-06-17
  Built the Email Atlas & Design System (landing, Atlas, Index, spec pages, components, tokens, contribute)
  Why Make the whole V2 program clear in one place and collaborable with outside developers/designers

Git feed — recent commits touching email files (40)