Skip to content

chore(plans): queue notifier-email (status: planned)#96

Merged
themightychris merged 1 commit into
mainfrom
chore/queue-notifier-plan
May 30, 2026
Merged

chore(plans): queue notifier-email (status: planned)#96
themightychris merged 1 commit into
mainfrom
chore/queue-notifier-plan

Conversation

@themightychris
Copy link
Copy Markdown
Member

Summary

Drops a `status: planned` plan file for #82 (real notifier — email-only first cut). Captures the design before we forget — Resend transport, `LoggingNotifier` as the unset-env fallback, template shape, env vars to add, deliverability warm-up + PII-in-logs risks.

Slack DM is split off as a follow-up tracked in #95 since it needs deeper Slack-integration credential work than the email leg.

Plan stays at `status: planned` until we pick it up — #32 (avatar upload) is taking next priority to prove the attachments-serving path end-to-end.

Test plan

  • N/A — doc-only

🤖 Generated with Claude Code

Captures the design for #82 ahead of implementation: email-only first
cut via Resend, with LoggingNotifier as the unset-env fallback so
dev + tests stay configuration-free. Slack DM is split into its own
follow-up issue (#95) until we have the deeper Slack-integration trust
in place (sending DMs out from a workspace bot is a different
credential shape than our existing SAML IdP relationship).

Plan stays at status: planned — #32 (avatar upload) gets picked up
next to prove the attachments-serving path end-to-end first.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@themightychris themightychris merged commit 0d99950 into main May 30, 2026
1 check passed
@themightychris themightychris deleted the chore/queue-notifier-plan branch May 30, 2026 02:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant