conventionlisted

# Extract conventions Inspect representative production code and tests, identify repeated architectural and implementation patterns, and write concise convention documents to the user-selected Codex-owned path. Cite concrete repository files, distinguish enforced rules from observations, and avoid changing application code unless the user explicitly asks. ## Workflow 1. Read the applicable `AGENTS.md` files and repository architecture documentation before analysis. 2. Resolve the requested scope: full repository, convention documents only, rule extraction from existing convention documents, or explicit paths. 3. Inventory languages, frameworks, module boundaries, build files, tests, migrations, and existing convention material with focused `rg` searches. 4. Select representative production and test files for each relevant layer. Prefer repeated current patterns over isolated legacy examples. 5. Record evidence for architecture boundaries, dependency direction, naming, data models, error handling, persistence, external integrations, testing, and deployment constraints. 6. For each candidate convention, cite concrete paths, state whether it is enforced or observed, identify exceptions, and name the preferred reference implementation. 7. Write compact English convention documents under the requested project `.codex/` path. Preserve unrelated content and do not duplicate full rule bodies in `AGENTS.md`. 8. If the user requests durable rules, extract accepted candidates, dedupl