standup
Standup — 2026-05-12
**Slice 7 shipped: Resend email notifications.** Three flavors of internal email are live.
Daily standup for 2026-05-12. What shipped:
Slice 7 shipped: Resend email notifications.
Three flavors of internal email are live. A post-deploy step in daily-standup.yml reads today’s standup markdown and sends the digest to the team via Resend’s HTTP API (direct fetch, no SDK). New questions, answers, and comments trigger ctx.waitUntil() fire-and-forget calls from the existing QnA endpoints — the D1 write succeeds first, email follows without blocking the response. A shared sendEmail() module handles all three paths; one email_log table (migration 0004, b1293d3) logs per-recipient delivery for observability. Templates are plain HTML — no framework.
Recipients are hardcoded for V1: comma-separated env var on the Workers side, GitHub Actions secret for the workflow. @blair-style mentions in a question or answer body promote the named recipient to position 0 and prepend [@you] to the subject. Author is excluded from their own notification.
Standup email path has one deliberate gap: the Node workflow runner can’t write to D1 directly, so standup sends don’t appear in email_log. Logged by design as a known deferred item — a thin Functions endpoint could backfill it if silent failures become a real problem.
Slideshow teaser tile and standalone /slideshow/ page also shipped (554220f).
Notable. The standup bot’s own CI had a bug (527d2af): new standup files weren’t being staged before the diff-check, so fresh files never committed. Fixed same session it was caught.
Window: 2026-05-11T13:00
→ 2026-05-12T03:19.373Z · Sources: memberintel @ noop, memberpress-intel @ 421d6b3