fix: Sentry reporting handled chunk load errors

[sentry]

Dynamic import failures (chunk load errors) due to version skew are correctly handled by stale-app-reload.ts, which forces a page reload. However, Sentry was still capturing these as unhandled exceptions, creating noise in error monitoring.

This PR exports staleAppErrorPatterns from src/utils/stale-app-reload.ts and passes it as the ignoreErrors array to Sentry.init in src/router.tsx. This ensures that Sentry will now silently drop these expected and already-handled errors, preventing them from being reported.

Fixes TANSTACK-COM-4AP

_{This PR was automatically generated by Sentry. You can adjust this setting at any time.}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	tanstack-com	8cd3cda	Commit Preview URL Branch Preview URL	Aug 29 2026, 11:04 PM

[tannerlinsley]

This catches the deployment noise, but it also hides failures when the reload cooldown prevents recovery. I added a narrower fix and regression coverage in #1327. Keeping this open until that replacement passes its checks and lands.

AI review notes: ignoreErrors matches the message regardless of whether reloadOnStaleAppError returned true. The SDK regression in #1327 verifies that the first handled error is suppressed and a new error during the 10-second cooldown is still reported, using an in-memory Sentry transport. No deployed-browser recovery is claimed.

[tannerlinsley]

Thanks for flagging the stale-chunk noise. #1327 has now landed with the narrower recovery check, so this implementation is superseded.

AI review notes: The merged change suppresses the exact error that triggered a reload and retains reporting for new errors during the cooldown. This replaces the blanket ignoreErrors proposal here. The original Sentry incident link and proposal remain in this PR for reference. This is a verified merge, not a claim that production deployment has finished.