component-conformance-reviewlisted

## What It Does Audits the project's UI components against `components.md`. The AST-derived component inventory is the subject; the contract is the standard. Every component used in source must appear in `components.md` with declared variants, states, and permitted compositions. Override sprawl (`!important`, inline `style=`, undocumented Tailwind combinations, shadcn primitives wrapped without spec) is a finding. ## Use This When Use this for every design-test run, after `token-conformance-review`. The two together form the "is the contract followed at the source level" pair. ## Inputs - Read `docs/instructions/design-system/components.md`. - Read the contract-summary from `design-system-coverage` (declared component clauses). - Read `references/component-conformance-checklist.md` before scanning. ## Procedure The set difference between source and contract is deterministic — drive it with the scripts. Reserve LLM judgment for severity and the "is this primitive correctly wrapped" question. 1. Run `scripts/derive-inventory.sh [components-dir]` → `<name>\t<source-file>` TSV. The script already excludes tests, stories, type decls, barrels, and lower-case helpers. 2. Run `scripts/parse-components-md.sh <components.md>` → `<name>\t<variants-csv>\t<states-csv>` TSV. Empty CSV slots are `-`. 3. Run `scripts/diff-inventories.sh --source <derived> --declared <parsed>`. Each row is a deterministic gap: - `in-source-not-declared\tName\t<file>` → `documentation-drift` finding