cc-safety-net AGENTS.md

• Use bun run check to verify when you finish all implementations at the end. This runs typecheck, knip, biome lint, and tests together; do not run these separately.
• Ignore the dist folder; it gets auto-rebuilt by lefthook's pre-commit hook.
• Keep implementation modular; put tests in tests/ mirroring src/, not colocated in src/.
• Files in docs/ use lowercase kebab-case names.

Scope Discipline

Over-engineering is this project's dominant failure mode. The evidence rule that governs analyzer rules governs all code: machinery exists to stop a demonstrated failure, not an imagined one.

• Implement the smallest change that satisfies the request. Each addition beyond it needs the concrete failure it prevents named; if you cannot name one, do not write it.
• Every check must be falsifiable in practice: name the realistic mistake that makes it fail. A check the same author can trivially satisfy while still making the mistake (self-reported attestations, digests over co-located data, matching UUIDs) is ceremony — do not add it.
• Do not build schemas, validators, registries, or harnesses ahead of their first real entry, and do not store fields whose values are forced constants or derivable from other fields.
• Prefer a documented process over code that enforces the process. Enforcement code is justified only after the documented process has demonstrably failed at least once.
• When remediating review findings, implement the smallest fix per finding. A finding is never a mandate to build a framework; if the fix seems to require one, stop and ask.

Code Review Rules

• Before reviewing, read REVIEW.md and apply its review criteria.

Style Guide

• Keep things in one function unless composable or reusable.
• Avoid try/catch, the any type, and else branches (prefer early returns).
• Rely on type inference; avoid explicit annotations or interfaces unless necessary for exports or clarity.
• Prefer functional array methods (flatMap, filter, map) over for loops; use type guards on filter to maintain type inference downstream.
• Inline values used only once instead of naming them.
• Prefer const over let; use ternaries or early returns instead of reassignment.
• Avoid unnecessary destructuring; use dot notation to preserve context.