* feat: add Sentry error monitoring (#77)
Installs and configures @sentry/react-router with server and client
instrumentation. Disabled in development to avoid noise; only active
in production.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* chore: add VSCode Sentry MCP server config
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix: pass vite env to sentryReactRouter plugin
sentryReactRouter requires the ConfigEnv as a second argument to read
the vite `command` property.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
* Improve error pages with styled, status-aware UI
Replace the bare-bones error boundary with a proper error page that:
- Renders a minimal Brackt header so users can navigate home
- Shows distinct messages and icons for 401, 403, 404, 500+ errors
- Displays a "Sign in from the home page" hint on 401 so logged-out
users know how to recover
- Hides internal details in production (stack traces dev-only)
- Uses existing dark theme Tailwind classes for visual consistency
https://claude.ai/code/session_011jv8desa5vhSkjZHSjWZiV
* Address code review feedback on error pages
- Move statusIcon out of ErrorBoundary render as a plain module-level
function to avoid React re-creating a component type on every render
- Collapse 401 action into a single descriptive button label
("Go to Home Page to Sign In") instead of a fragmented button + hint
- Fix details/summary border radius collision by using overflow-hidden
on the container and removing rounded-md from the summary element;
separate the pre block with a border-t instead
https://claude.ai/code/session_011jv8desa5vhSkjZHSjWZiV
---------
Co-authored-by: Claude <noreply@anthropic.com>
