R15.1: React error boundary protection

Short answer: Major route segments wrapped in error boundaries. One failing component should not blank the whole page.

Group: Error boundaries and fallback rendering. Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R15.1

What it catches

React error boundary protection: major route segments wrapped in error boundaries.

Why

One failing component should not blank the whole page.

A bad example

<Dashboard />

A good example

<ErrorBoundary fallback={<Retry />}><Dashboard /></ErrorBoundary>

How it is checked

Nothing yet. No scanner and no slice card checks it: it is a standing rule for authors and reviewers.

How to silence it

A person can silence one finding with brevio-core: ignore R15.1 -- reason on the line or the line above. Without the reason it does not count. An agent cannot silence it: the agent hook and the MCP tools never honour the comment, and a pull request that adds one is reported until a reviewer allows it. Fixing the code is still the better answer.

To change what the rule flags, edit its definition in dev_rules.py or code_rules/__init__.py. That is a code change and is reviewed like one.

R15.2 Non-blocking third-party failures
R15.3 Form submit recovery
R15.4 Image broken state fallback
R15.5 Network offline banner
Every rule