Plan 21-01 Summary: Error Boundary & Toast Notifications

Result: COMPLETE

Duration: ~3 min Commits: 2

Created ErrorBoundary component (packages/web/src/components/ErrorBoundary.tsx)
- React class component with getDerivedStateFromError and componentDidCatch
- Renders centered error card: red AlertCircle icon, "Something went wrong" heading, error message in muted text, Reload button
- Styled with existing Tailwind classes matching the app's error state patterns
Created Sonner toast wrapper (packages/web/src/components/ui/sonner.tsx)
- Thin wrapper exporting Toaster component from sonner
- Configured with position="bottom-right" and richColors
Wired into root route (packages/web/src/routes/__root.tsx)
- <ErrorBoundary> wraps <Outlet /> inside AppLayout so route-level render errors are caught without destroying the nav shell
- <Toaster /> rendered as sibling to AppLayout for app-wide toast availability
- notFoundComponent updated with "Back to Dashboard" Button/Link pointing to /initiatives
Wired toast notifications into all mutation flows
- SpawnArchitectDropdown.tsx: toast.success("Architect spawned") on success, toast.error("Failed to spawn architect") on error
- ActionMenu.tsx: toast.success("Initiative archived") on success, toast.error("Failed to archive initiative") on error
- CreateInitiativeDialog.tsx: toast.success("Initiative created") on success (inline error kept for form validation)
- inbox.tsx: toast.success/toast.error for both resumeAgent and respondToMessage mutations

21-01: ErrorBoundary wraps Outlet only (not entire AppLayout) so nav shell survives render errors
21-01: Toaster outside AppLayout as sibling — available even if layout breaks
21-01: notFoundComponent uses shadcn Button with asChild + Link (consistent with component library)
21-01: CreateInitiativeDialog keeps inline form error in addition to toast (inline error shows specific validation message)
21-01: One success and one error toast per mutation — no toasts for query failures (those have inline error states)