brevio-core

Catches the mistakes coding agents repeat before they merge: a pull-request gate with no model call and no API key.

View the Project on GitHub Brevio-Ventures/brevio-core

R7.5: Universal contracts purity

Short answer: Contracts barrels must not import Node built-ins (node:fs, node:path). The client bundler cannot load Node built-ins, so one import in a shared barrel breaks the web build.

Group: Architecture and contracts. Status: stable. Generated from the rule definitions; do not edit by hand.

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

What it catches

Universal contracts purity: contracts barrels must not import Node built-ins (node:fs, node:path).

Why

The client bundler cannot load Node built-ins, so one import in a shared barrel breaks the web build.

A bad example

import fs from 'node:fs';

A good example

import { z } from 'zod';

How it is checked

How to silence it

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

What the scanner already leaves alone: Server-only files (drift.ts, *-io.ts, *-node.ts, server/) 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.