Handle null Copilot notification responses

[cursor]

Changes

• Treat null Copilot notification responses as expected for email-only delivery targets.
• Keep in-product notification deliveries strict by throwing a clear error if Copilot returns no notification resource.
• Guard notification persistence paths so nullable email-only responses are not written as notification records.
• Add focused coverage for null email-only and null in-product responses.

Testing Criteria

• yarn test src/utils/CopilotAPI.test.ts --runInBand
• yarn lint:check (passes with existing warnings)
• yarn tsc --noEmit --pretty false (blocked by pre-existing SVG module declaration errors in src/icons/index.ts)

Notes

• Investigated Linear OUT-3801 / Sentry TASKS-8R. Sentry events are from the tasks project and the issue was created in Triage.
• Linear MCP authentication is expired, so I could not post the requested ticket comment from this environment.

Impact & Surface Area of Change

• Affects Copilot notification creation and downstream notification persistence paths.
• Email-only reminder deliveries can now complete without raising a ZodError when Copilot returns null instead of a notification resource.
• In-product notification flows still require a persisted Copilot notification object and will fail loudly if Copilot returns none.

  

[linear-code]

OUT-3801

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview, Comment	May 30, 2026 12:16am