Add a route-level error boundary for Next.js App Router segments
Next.js route segments should declare an error.tsx handler so async and client failures surface safely.
#Metadata
#Why it matters
Without a segment error boundary, failures in pages or layouts can crash the entire subtree without recovery UI.
#Remediation
Add error.tsx next to the segment’s page or layout, or hoist shared handling to a parent segment.
#Repository path
The generated metadata points to critiq-rules/libs/rules/catalog/rules/typescript/ts.react.no-missing-error-boundary.rule.yaml.