wikilisted

# Wiki Rebuild Use the `wiki` MCP tool as the source of truth. This skill is only a workflow wrapper; do not invent a separate wiki structure. The generation prose — discovery rules, the source-first writing contract, the self-check, and the per-page prompts (flow, screen, overview) — is served from markdown, using packaged defaults unless a project overrides them. To customize it for a project, run `wiki(eject)` once: it writes the defaults to `.mimirs/wiki/*.md` for you to edit, and a file there overrides the packaged default. Edit instructions in `.mimirs/wiki/`, never the generated `wiki/` output. ## Core Rule The wiki is flow-first. Create one page for one concrete trigger: - one HTTP method + route - one message, event, queue topic, or consumer handler - one CLI subcommand - one MCP tool - one worker, job, schedule, webhook, or server start Do not bundle all API endpoints into one page. Do not bundle all messages into one page. Do not create broad architecture, module, entity, glossary, or generic data-flow pages unless the human explicitly asks for those. If many flows share files, keep separate pages and connect them with related flows. ## Workflow 1. Call `index_files()` if the project index is empty or stale. 2. Call `wiki(shape)`. 3. Use the returned prompt and prefetch selectors to create `wiki/_discovery.json`. 4. Validate with `wiki(validate-discovery)`. 5. If validation reports errors, fix `wiki/_discovery.json` and validate again. 6. If validation pas