Release v0.1.11: Notification System (Email, Slack, Discord)

February 11, 2026

What changed

• Multi-channel notifications — Email (via Resend), Slack (webhooks), and Discord (webhooks) are now supported
• 5 notification events: pipeline complete, pipeline failure, approval required, release published, and feature discovered
• Settings UI added as a new "Notifications" tab on the project detail page with per-channel, per-event toggles and a test button
• All 4 agents (documentation, implementation, testing, release) now dispatch notifications on key events
• New DB migration (0005_notification_settings.sql) and tRPC router for notification settings CRUD
• Zero new dependencies; uses raw fetch() for all external calls
• Non-blocking: notification failures are logged but never crash pipelines (Promise.allSettled)

Why it matters

You no longer need to check the dashboard to know what's happening. Pipeline completions, failures, and approval gates now come to you wherever you work.

Technical notes

• New env vars: RESEND_API_KEY and RESEND_FROM_EMAIL (required only for email notifications)
• Slack/Discord require no server-side config — users provide webhook URLs in the UI
• Webhook URL validation enforces correct Slack (hooks.slack.com) and Discord (discord.com/api/webhooks/) prefixes
• Email falls back to the user's Clerk account email if no address is specified
• +1,343 / -3 lines across 12 files