Catches the mistakes coding agents repeat before they merge: a pull-request gate with no model call and no API key.
Short answer: Never leave [data-reveal] at opacity:0 without CSS animation fallback. If scripts load late, an element that starts at opacity 0 stays invisible for the visitor.
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.2
SSR visibility resilience: never leave [data-reveal] at opacity:0 without CSS animation fallback.
If scripts load late, an element that starts at opacity 0 stays invisible for the visitor.
[data-reveal] { opacity: 0; }
[data-reveal] { opacity: 0; animation: show 0s 1s forwards; }
@keyframes show { to { opacity: 1; } }
dev_rules.scan_added_lines); brevio-core scan does not run it.dev_rules.slice_micro_rules).A person can silence one finding with brevio-core: ignore R1.2 -- 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.
What the scanner already leaves alone: A file that holds a @keyframes block is not flagged.
A scan reads only the lines you add, so a line that was already in the file is not flagged.
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.