Error boundaries exist around high-risk feature sections

A root error boundary keeps the shell alive, but without feature-level boundaries a single crashing widget still takes down the entire dashboard, settings panel, or payment form. ISO 25010 reliability.fault-tolerance expects fault isolation: one failed revenue widget should not blank the user analytics widget beside it. Applications with data tables, real-time feeds, and payment forms are the highest-risk areas — each independently capable of crashing a page and forcing the user to reload and start over.

Wrap each high-risk feature section in its own ErrorBoundary. In Next.js App Router, add error.tsx files inside each route segment directory; in other apps, use react-error-boundary at the component level.

// app/dashboard/error.tsx — dashboard-scoped boundary
'use client'
export default function DashboardError({
  reset,
}: {
  reset: () => void
}) {
  return (
    <div>
      <p>Dashboard failed to load.</p>
      <button onClick={reset}>Retry</button>
    </div>
  )
}

Target at minimum: dashboard, checkout/payment form, and any real-time feed — these three account for the highest crash frequency in vibe-coded apps.