template-validation-quality

# Validation quality Prefer **actual CLI entrypoints** in [`CLAUDE.md`](../../../CLAUDE.md) — not illustrative Python stubs. ## Natural invoke - "Validate markdown under projects/templates/template_prose_project/manuscript/" - "PDF has unresolved references — run validation" - "Strict prerender before render" ## Inputs to confirm - **Target** — manuscript dir, PDF path, or `output/<project>/`. - **Project** — from active_projects when path ambiguous. ## Workflow 1. **Source markdown** — `infrastructure.validation.cli markdown` and/or `prerender`. 2. **Citations** — `infrastructure.reference.citation validate` on `.bib`. 3. **Links** — `infrastructure.validation.cli links --repo-root .` 4. **PDF** — after render: `cli pdf output/<project>/pdf/` 5. **Integrity** — `cli integrity output/<project>/` 6. **Report** — diagnostic codes from validation; path + fix per issue. ## Deliverables - Command list with exit codes - Issue table: code | file | message | fix ## Verification commands ```bash uv run python -m infrastructure.validation.cli prerender projects/<project>/manuscript --repo-root . uv run python -m infrastructure.validation.cli markdown projects/<project>/manuscript --repo-root . --strict uv run python -m infrastructure.reference.citation validate projects/<project>/manuscript/references.bib uv run python -m infrastructure.validation.cli links --repo-root . uv run python -m infrastructure.validation.cli pdf output/<project>/pdf/ uv run python -m infrastruc...