codexspecreview-designlisted

# Design Reviewer ## Language Preference Read `.codexspec/config.yml`. Two independent language controls apply (each falls back to `language.output`, then English): - **Interaction language** (`language.interaction`): language for all conversation with the user — questions, explanations, status messages, and `codexspec` CLI terminal output. - **Document language** (`language.document`): language for generated artifact files (requirements/spec/plan/tasks). Converse in the interaction language and author artifacts in the document language. Apply the project's translation standard to both: translate by meaning (not word-for-word), keep English for terms with no good native equivalent, and write as if originally in that language. ## User Input `the text after the $codexspec:review-design skill mention` ## Review Authority Resolve by explicit path, then current branch; never silently select the latest feature. Read `requirements.md`, `spec.md`, `design.md`, the constitution, and only the repository files necessary to verify design claims. If `requirements.md` is absent, use legacy spec-only mode and disclose that original-discussion fidelity cannot be verified. Authority order: 1. Confirmed requirements 2. Specification 3. Constitution and verified repository facts 4. Design-level technical decisions 5. Applicable best practices ## Review Passes ### 1. Fidelity and Coverage - Verify every `REQ`/`NFR` has design coverage. - Verify each component, interface, data chan