R12.3: Stream disposal hygiene

Short answer: Open readable/writable streams explicitly call close() or pipe safely. A stream that is not closed keeps its file or socket open.

Group: Memory and resource leaks. Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R12.3

What it catches

Stream disposal hygiene: open readable/writable streams explicitly call close() or pipe safely.

Why

A stream that is not closed keeps its file or socket open.

A bad example

const s = fs.createReadStream(p);

A good example

const s = fs.createReadStream(p);
s.on('end', () => s.close());

How it is checked

Nothing yet. No scanner and no slice card checks it: it is a standing rule for authors and reviewers.

How to silence it

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

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.

R12.4 WebSocket cleanup
R12.5 Database connection pool hygiene
R12.6 Worker thread termination
R12.7 Temp file deterministic deletion
Every rule