Server Component errors now traceable with Sentry digests

Error digests are now captured in Sentry tags, allowing you to cross-reference with Vercel runtime logs to debug root causes.

Bug Fixes

Server Component render errors on /dashboard were previously undebuggable in Sentry. Next.js provides a digest property that maps errors to Vercel's runtime logs, but Sentry wasn't capturing it.

We now extract the error digest and forward it as an errorDigest Sentry tag. When errors occur, you can query the tag in Sentry and cross-reference with vercel logs to recover the underlying server-side error details.