There is no ErrorBoundary anywhere in the app (grep found zero componentDidCatch / error-boundary). A single unhandled render error unmounts the whole tree (the React console even suggests adding one: 'Consider adding an error boundary to your tree').
Work needed:
- Add a top-level ErrorBoundary wrapping the router
- Per-route fallback UI (a friendly 'Something went wrong' card with reload)
- Optional: Sentry/error reporting hook on catch
Why: improves resilience and is the fix suggested by the ArchitectureMap crash earlier (ReactFlow provider error took down the tree).
There is no ErrorBoundary anywhere in the app (grep found zero componentDidCatch / error-boundary). A single unhandled render error unmounts the whole tree (the React console even suggests adding one: 'Consider adding an error boundary to your tree').
Work needed:
Why: improves resilience and is the fix suggested by the ArchitectureMap crash earlier (ReactFlow provider error took down the tree).