Context
Empty states and alerts do not fully cover failed data regions. Tables, cards,
charts, and full pages need consistent recovery guidance without always invoking
the application-level ErrorBoundary.
Scope
- Add inline, section, and page ErrorState layouts.
- Support title, safe description, retry action, secondary action, and optional error reference.
- Define recoverable, permission, offline, and unavailable presentation variants.
- Ensure internal error details are not exposed to users by default.
Acceptance criteria
- Retry supports loading and disabled states and prevents duplicate activation.
- Error reference can be copied without exposing stack traces.
- Offline and permission variants provide specific, actionable guidance.
- Inline layout works inside tables, cards, and dialogs.
- Tests cover variants, retry lifecycle, copy action, and accessible alert semantics.
Out of scope
- Replacing React ErrorBoundary for render crashes.
- Logging errors or selecting an observability provider.
Context
Empty states and alerts do not fully cover failed data regions. Tables, cards,
charts, and full pages need consistent recovery guidance without always invoking
the application-level ErrorBoundary.
Scope
Acceptance criteria
Out of scope