// changelog

v1.11.0

Architecture-aware review. When a repo ships an `architecture.json` — the config of the sibling tool archlint, declaring layers and their allowed import edges — CommitBrief reads it and feeds a compact summary of the layers and their forbidden boundaries into the review prompt, so the reviewer can flag a diff that crosses a declared architectural boundary. A one-way read; CommitBrief never lints or enforces.

Released June 21, 2026

Added

Architecture-aware review (ADR-0030). When a repo ships an architecture.json — the public config of the sibling tool archlint, declaring layers (path prefixes) and rules (allowed import edges) — CommitBrief now reads it and injects a compact, deterministic summary of the layers and their allowed/forbidden boundary edges into the review prompt as a distinct <architecture_constraints> block. The reviewer can then flag a diff that crosses a declared boundary — e.g. “this adds domain → db, which the architecture forbids”.
```
{
  "layers": { "domain": ["internal/domain"], "db": ["internal/db"] },
  "rules":  { "domain": [], "db": ["domain"] }
}
```
It is a one-way read of archlint’s config — CommitBrief never lints the import graph or enforces anything itself (run archlint check in CI for the deterministic gate); it only grounds the LLM so it can reason about the change. A missing or malformed file is a transparent no-op that never breaks a review.
On by default (review.architecture, default true); the discovery path is overridable via review.architecture_file; opt out per-run with --no-architecture. The block folds into the system prompt, so editing architecture.json invalidates stale cached reviews while a repo without the file keeps a byte-identical cache key — no mass invalidation. Applies to review and dry-run. No new dependency.