Replace Next.js default error boundary with custom error pages that preserve navigation and provide better UX.
**Problem:**
- Default Next.js error boundary shows generic message with NO navigation
- Users have no way to recover or navigate away from error
- Message: "Application error: a client-side exception has occurred (see the browser console for more information)."
**Solution:**
- Add custom error.tsx at root level with navigation links
- Add custom error.tsx in /arcade with PageWithNav component
- Both provide:
- Clear error message
- "Try Again" button to reset error boundary
- Navigation links (home, arcade lobby)
- Collapsible technical details for debugging
**Benefits:**
- Users can always navigate away from errors
- Arcade errors keep the nav bar for consistent UX
- Root errors provide basic navigation links
- Professional error pages instead of generic Next.js message
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
73cc4185c3