loupe-documentslisted

# Writing documents for Loupe review Reviewers read what you send to `document_create` / `document_revise` in the Loupe review UI, where they select passages and comment on them. Format for that reading context, not for a terminal or a README. ## Rules 1. **No H1 title in the body.** Loupe's own `title` field holds the title, so an `# Heading` repeating it renders twice. Start with content, or with the first `##` section. 2. **Prefer numbered lists over bullet lists.** Reviewers cite entries in comments ("point 3 is wrong"), which numbers permit and bullets do not. Use bullets only where order and reference genuinely do not matter, such as a short set of interchangeable examples. 3. **Cross-references need stable IDs, because list numbering restarts at every heading.** Markdown starts a new ordered list after each `##`, so source entries numbered 1–33 render as 1–2 under the first heading, then 1–5 under the next, and a "see finding 6" points at nothing the reviewer can see. A self-hosting audit shipped with every cross-reference broken, and the reviewer's first comment was that finding 6 did not exist. When entries refer to one another, give each a short ID that does not depend on rendering: `C1`, `H4`, `M5` for severity-banded findings, or any scheme where the prefix names the section. Lead the entry with it: ```markdown 4. **H4 — There is no administrative console command.** … ``` Refer to **H4**, never "finding 4"