Add global error boundary with Sentry integration and fallback UI

[Kingsman-99]

Overview

Unhandled React render errors crash the entire app silently. Add a root-level error boundary with a user-friendly fallback UI and Sentry error reporting so crashes are captured and actionable.

Acceptance Criteria

• Root ErrorBoundary component wraps the entire app in layout.tsx
• Fallback UI: friendly message ("Something went wrong"), error ID, "Reload Page" button, "Go to Dashboard" link
• Error ID shown to user matches the Sentry event ID for support correlation
• Sentry SDK (@sentry/nextjs) configured with DSN from NEXT_PUBLIC_SENTRY_DSN env var
• Error boundary catches errors and calls Sentry.captureException(error) before rendering fallback
• Route-level error boundaries (error.tsx in each route segment) for scoped errors that don't crash the whole app
• Sentry source maps uploaded on next build so stack traces resolve to original TypeScript
• Sentry integration disabled in development (no DSN required locally)
• User session, wallet address (hashed), and current route included in Sentry context

[dotmantissa]

Hi maintainers,

I'd like to work on this. I'll add a root ErrorBoundary in layout.tsx with a friendly fallback showing the Sentry event ID, a reload button, and a dashboard link, configure the Sentry SDK with DSN from the env var, hash the wallet address before including it in context, add route level error.tsx boundaries for scoped errors, disable Sentry in development, and wire source map uploads into the build.

I estimate I can have a PR ready within 4 hours of being assigned. Could you please assign this to me?

Thanks.

[Emelie-Dev]

@Emelie-Dev has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I would love to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Emelie-Dev to this issue.

[lonerthefirst3-sudo]

@lonerthefirst3-sudo has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

i would love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @lonerthefirst3-sudo to this issue.

[drips-wave]

Congratulations, @lonerthefirst3-sudo! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @lonerthefirst3-sudo: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊