docs-checklisted

# Docs Check Validate the GitHub Pages documentation site produced by `@docmd/core`. ## Quick Reference | Step | Check | Command | | --- | --- | --- | | 1 | Build | `npx @docmd/core build` | | 2 | Orphans | `comm -23 <(find docs/ -name '*.md' \! -name 'index.md' \| sort) <(rg -o '\([^)]+\)' docs/index.md \| rg -o '[^()]+' \| sort)` | | 3 | ADR index | Cross-ref `docs/ADR/adr-*.md` vs `docs/ADR/index.yaml` | | 4 | LLM audit | Check `site/llms.txt`, `site/llms-full.txt`, `site/llms.json` | | 5 | Preview | `npx @docmd/core dev` | ## Prerequisites - Node.js 18+ (for `npx @docmd/core`) - The repo root as working directory - Optional: `npx serve` or similar for local preview ## Mindset Documentation is only as valuable as it is discoverable. A broken build, orphan pages, missing index entries, and stale references each silently erode trust in the site. Treat every check as a gate: if it fails, the user loses confidence. - **Build first, ask questions later.** Always start with the build check — it is the fastest path to failure and catches mechanical issues early. - **Automate what you check twice.** If you catch the same issue twice, TYPICALLY you should add a script or CI step so you NEVER check it manually again. - **Fix the source, not the output.** When a check reveals a problem, fix the markdown source, not the built `site/` — the build is ephemeral. - **Escalate to the right skill.** When content quality issues surface, redirect to `markdown-authoring`; when skill do