R9.2: No silenced type errors

Short answer: No @ts-ignore; every @ts-expect-error states its reason. A silenced error hides a real bug, and nobody remembers why.

Group: Type safety. Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R9.2

What it catches

No silenced type errors: no @ts-ignore; every @ts-expect-error states its reason.

Why

A silenced error hides a real bug, and nobody remembers why.

A bad example

// @ts-ignore
const a = b.c;

A good example

// @ts-expect-error -- the library types omit this field
const a = b.c;

How it is checked

brevio-core scan: a scan of added lines (code_rules.scan_added_lines_for_rules).
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 R9.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.

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.

R9.3 Package-name imports
R9.1 No untyped escape hatches
Every rule