Contents
PR Summary
What problems was I solving
The management-ui package still carried ErrorBoundaryDefaultFallback, ErrorBoundaryWithDefaultFallback, and an ErrorBoundaryProps type re-export that had no remaining consumers in the package. These symbols were left behind after earlier refactorings stripped the old layouts that used them, contributing noise to the components barrel and making the file harder to reason about.
What user-facing changes did I ship
None. The removed components were not rendered anywhere in management-ui. The still-used ErrorBoundary component from @sentry/react continues to be re-exported and used by the analytics and overview pages with their own custom fallbacks.
How I implemented it
Deleted the unused component definitions and type re-export from architect/management-ui/app/main/components/error-boundary-with-default-fallback.tsx while preserving export { ErrorBoundary } so the components barrel still supplies the symbol used by analytics-page.tsx and overview-page.tsx.
Description for the changelog
Removed the unused ErrorBoundaryDefaultFallback, ErrorBoundaryWithDefaultFallback, and ErrorBoundaryProps re-export from the management-ui components module. The ErrorBoundary re-export is retained and remains available through the components barrel.