Filter pushstate browser noise from Sentry

[cursor]

Changes

• Added a shared browser Sentry ignore list for client-side ignored errors.
• Added NS Pushstate prevention to the client ignored-error patterns so browser/Next/Sentry history instrumentation noise no longer creates Tasks Sentry issues.
• Added focused unit coverage for the pushState noise, existing fetch noise, and unrelated application errors.

Testing Criteria

• yarn test src/utils/sentryIgnoredErrors.test.ts --runInBand passed.
• yarn lint:check passed with existing warnings only.
• yarn tsc was run; it is still blocked by pre-existing SVG module declaration errors in src/icons/index.ts, with no new diagnostics from this change.

Notes

• Linear/Sentry direct reads were unavailable in this automation environment: Linear MCP returned 401 and Sentry MCP requires authentication. The trigger payload showed the issue in Triage, and next.config.js confirms Sentry uploads for project tasks.

Impact & Surface Area of Change

• Client Sentry initialization only. Regression focus is limited to Sentry event filtering: generic fetch failures and NS Pushstate prevention are dropped, while normal application errors should continue to report.

  

[linear-code]

POR-21031

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview, Comment	Jul 8, 2026 6:00pm