Skip to content

v2.1.1 — allow_conflict: opt-out for aggregator topics

Choose a tag to compare

View all tags
@OoneBreath OoneBreath released this 19 Jun 00:35
· 14 commits to main since this release
v2.1.1
2b3a124

Patch release — a narrow opt-out for the conflict detector. Backward compatible: brains without the new field behave exactly as before. Still zero runtime dependencies.

Added

  • allow_conflict: frontmatter on a topic. brain-check flags a project that names two mutually-exclusive techs (a relational DB, a host) — but an aggregator topic (an infra topology map, a multi-repo roadmap/checklist) legitimately lists several at once. Opt a group out with allow_conflict: [relational-db] (or true for all groups). It is narrow: only that topic's tokens are excluded from the tally, so genuine drift in other topics still surfaces. An inline # comment after the value is tolerated; an unknown group name is warned.

Fixed

  • Aggregator topics no longer raise a permanent false-positive conflict warning that no note could silence (e.g. an infra server-topology that maps each project's DB across MariaDB / Postgres / SQLite).

Full changelog: https://github.com/OoneBreath/claude-code-project-brain/blob/main/CHANGELOG.md

Assets 2
Loading