consistency-check

Cross-document inconsistencies in game design documents are detected by comparing registered entity definitions in `design/registry/entities.yaml` against values in `design/gdd/*.md` files. The scan uses a grep-first approach to find conflicting values for items, formulas, or constants.

Targeted checks for a specific entity or item are supported during GDD authoring. The scan loads the registry once and uses targeted grep to scan only relevant GDD sections, allowing you to catch design drift before downstream architecture work.

The best way to resolve GDD conflicts involves a resolution workflow that updates `design/registry/entities.yaml` interactively. The scan classifies conflicts and performs deep reads only on detected mismatches to determine whether the fix belongs in the GDD or the registry.

Design consistency failures are logged to `docs/consistency-failures.md`. The scan produces a structured PASS or CONFLICTS FOUND report, supports interactive registry corrections, and automatically records detected cross-document value mismatches in the failure log.

An entity registry like `design/registry/entities.yaml` is required. The scan applies a registry-first greedy approach, loading registered entity, item, formula, and constant definitions once to compare them against GDD markdown files.

A since-last-review scan is used to check only recent changes, whereas a full scan validates the entire project. Both modes compare the entity registry against GDD markdown files to prevent design drift and catch conflicting values before they spread.