R9.3: Package-name imports

Short answer: Import workspace packages by name, never via ../../packages/ paths. A path that climbs into packages/ skips the package’s exports map and build boundary.

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.3

What it catches

Package-name imports: import workspace packages by name, never via ../../packages/ paths.

Why

A path that climbs into packages/ skips the package’s exports map and build boundary.

A bad example

import { Button } from '../../packages/ui/button';

A good example

import { Button } from '@acme/ui';

How it is checked

The harness’s pre-flight scan of added lines (dev_rules.scan_added_lines); brevio-core scan does not run it.
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.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: Comment lines are 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.

R9.1 No untyped escape hatches
R9.2 No silenced type errors
Every rule