Fix reminder suppression handling (OUT-3994)

[cursor]

Changes

• Treat a successful Copilot response with no created reminder notification as a terminal no-op instead of a retryable exception
• Preserve reminder ledger rows when individual or grouped reminder delivery is suppressed
• Keep actual Copilot errors retryable and covered by existing failure compensation
• Add unit and real-Postgres integration coverage for suppression behavior

Testing Criteria

• Focused individual and grouped reminder suites: 22 tests passed
• Reminder idempotency integration suite against Postgres 16: 4 tests passed, including ledger preservation and no Sentry capture on suppression
• ESLint passed with 35 existing warnings; Prettier check passed

Notes

• yarn tsc remains blocked by the repository's existing missing SVG module declaration errors in src/icons/index.ts; no errors referenced changed reminder files.
• No config or dependency changes are required.

Impact & Surface Area of Change

• Individual and grouped Trigger.dev reminder dispatches now distinguish a suppressed/no-op Copilot result (sent: false) from a delivery error. Delivery errors still retry and compensate ledger rows after retries are exhausted.

  

[linear-code]

OUT-3994

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview, Comment	Jul 15, 2026 12:14am