Catches the mistakes coding agents repeat before they merge: a pull-request gate with no model call and no API key.
Short answer: Never use waitForTimeout/sleep in tests. A sleep is either too short (flaky) or too long (slow).
Group: Testing and hermeticity. Status: preview. In a precision run on open-source repositories most of its hits were deliberate waits (a test checking that nothing happens in a given time) or test code written as a string, so it reports but never fails a scan until it can tell those from a sleep that stands in for a condition. Generated from the rule definitions; do not edit by hand.
Playground: https://brevio.pro/tools/agent-guard-playground?rule=R6.3
Deterministic condition waits: never use waitForTimeout/sleep in tests.
A sleep is either too short (flaky) or too long (slow).
await page.waitForTimeout(2000);
await expect(page.getByText('Saved')).toBeVisible();
brevio-core scan: a scan of added lines (code_rules.scan_added_lines_for_rules).dev_rules.slice_micro_rules).A person can silence one finding with brevio-core: ignore R6.3 -- 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: Only added lines in a file whose path contains ‘test’ are checked.
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.