Agent rule pattern
Baselines that may only shrink and lists that may only grow.
A known-violations file may only shrink; a tombstone list may only grow. CI usually enforces the direction.
Name the baseline and the only direction it may move. Include the enforcement command and any gaps that still need review.
The known-violations baseline may only shrink, while tombstone lists may only grow. Removing a violation requires deleting copies, adding a tombstone and adversarial fixture, registering consumers, and updating the audit.
Source excerpt starting at line 104.explicit `@hunk/vcs/*` leaves. The known-violations baseline is shrink-only: fix an edge, rerun `bun run deps:baseline`, and never add to it.
Because lint runs with --quiet, a package-wide downgrade to warning would look configured while enforcing nothing. The file connects this to a shared rule and a shrinking debt baseline.
Source excerpt starting at line 283.raises rules to `error`, and blocks scoped to `files`. It must not turn a ruledown for the whole package: every lint script runs with `--quiet`, so a `warn`enforces nothing and reads as if it did. The code-health rule`lint-config-layering` enforces this, with existing debt in`.code-health-baseline.json`, which only shrinks.
Published codecs may not gain, reorder, or reinterpret fields; incompatible changes need a new name. Digest tests miss appended enum variants, so reachable enums remain closed even when tests pass.
Source excerpt starting at line 94.- Existing-value digests cannot detect an appended enum variant. Review every enum reachable from a frozen codec as append-closed even when tests remain green.
hunk 
n8n 
herdr 
