3 commits

Author	SHA1	Message	Date
Ullrich Schäfer	ef07915f38	Add Sentry error tracking to both apps ... Planner (client + custom server) and Journal (client + entry.server): - Client: @sentry/react with browser tracing + replay on error - Server: @sentry/node for unhandled exceptions - ErrorBoundary captures React errors via Sentry.captureException - Disabled in dev, 10% trace sample rate in production Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-25 02:35:16 +01:00
Ullrich Schäfer	dee6f2806f	Add root ErrorBoundary to both apps, simplify withDb ... Both apps now have proper ErrorBoundary exports in root.tsx: - 404: "Page not found" - 503: "Service temporarily unavailable" - Other: shows error message Simplified withDb re-throw check: anything with a "status" property is treated as a React Router response (covers Response and ErrorResponseImpl). DB errors throw a plain Response(503) that the error boundary renders nicely. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-25 00:06:10 +01:00
Ullrich Schäfer	30d40de7cf	Complete monorepo toolchain setup (tasks 1.1-1.7) ... - Turborepo + pnpm workspaces with catalog for shared dependency versions - TypeScript strict config (base + per-package extends) - Tailwind CSS v4 via @tailwindcss/vite plugin - ESLint + Prettier shared config - Planner app scaffolded with React Router 7 (port 3001) - Journal app scaffolded with React Router 7 (port 3000) - Both apps build and start successfully via turbo Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-22 12:12:57 +01:00