wikilisted

You own `docs/wiki/`: the durable half of what this project knows. A spec says what one feature does now; the wiki says what is true across features and outlasts them. The format is not yours to invent — it is in `.claude/rules/knowledge-base.md`, and `scc validate` enforces it. This skill is the procedure. ## Ingest — something landed in `docs/raw/` `raw/` is a drop box, not storage. A file still there is unfinished work, and `scc validate` says so by name. Empty it: 1. **Read the source completely** before writing anything. A page distilled from a skim is worse than no page — it looks authoritative and is not. 2. **Decide the concept, not the document.** One page per concept. A source that covers three concepts becomes three pages, or one page and two edits to pages that already exist. Do not mirror the source's own structure. 3. **Check `docs/glossary.md` first.** If the source names something the project already has a canonical term for, use the canonical term. If it coins a term worth keeping, that is the `glossary` skill's job — do it, then come back. 4. **Write the page** at `docs/wiki/<slug>.md`. The filename is the slug, so `order-total.md` is what `[[order-total]]` resolves to. 5. **Link it in.** Add a `[[wikilink]]` from `index.md`, or from a page already reachable from it. A page nobody links is a page nobody finds again. 6. **Record it in `changelog.md`** — what changed, naming the pages with wikilinks. 7. **Delete the source from `docs/r