R1.5: No dead controls

Short answer: Every interactive element wires a handler and loading/error feedback. A button that does nothing, or hides a failure, teaches people the product is broken.

Group: UI and mobile performance. Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R1.5

What it catches

No dead controls: every interactive element wires a handler and loading/error feedback.

Why

A button that does nothing, or hides a failure, teaches people the product is broken.

A bad example

<button>Save</button>

A good example

<button onClick={save} disabled={saving}>{saving ? 'Saving' : 'Save'}</button>

How it is checked

A one-line card in the prompt of a slice that touches matching files (dev_rules.slice_micro_rules).

How to silence it

A person can silence one finding with brevio-core: ignore R1.5 -- 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.

R1.6 Accessible switch geometry
R1.7 LCP asset priority
R1.8 Async polling hygiene
R1.1 Mobile GPU budget
Every rule