Fix notification count validation without Tasks app id

[cursor]

Changes

• Parse COPILOT_APP_ID/legacy COPILOT_APP_API_KEY as an optional UUID instead of throwing a raw ZodError.
• Skip client notification-count reconciliation when the Tasks app id is not configured, avoiding unsafe cross-app cleanup.
• Keep Copilot notification lookup scoped to the configured Tasks app id when present.
• Add focused regression tests for missing app id and app/company filtering.

Testing Criteria

• yarn test "src/utils/CopilotAPI.notifications.test.ts" "src/app/api/notification/validate-count/validateCount.service.test.ts" --runInBand
• yarn lint:check
• yarn tsc --noEmit attempted; fails only on the known pre-existing SVG module declaration errors from src/icons/index.ts.

Notes

• Linear/Sentry source details could not be fetched directly because Linear MCP returned auth_revoked and Sentry MCP requires authentication. The fix addresses the matching raw ZodError: [ path found in Tasks notification validation.
• Runtime config should prefer COPILOT_APP_ID; COPILOT_APP_API_KEY remains as a legacy fallback only if it contains a UUID.

Impact & Surface Area of Change

• Affects the client notification-count validation route and Copilot notification filtering only.
• Main regression area: client notification badge/count reconciliation for environments with a configured Tasks app id.

  

[linear-code]

OUT-3904

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview, Comment	Jun 24, 2026 1:31pm