wiki-ingestlisted

# Ingest sources Turn supplied material into grounded, cross-linked pages without changing the source. The knowledge base's `inbox/` is the staging area; its `.raw/captured/` holds the immutable copy of every source it captured. Tools: `status`, `inbox`, `capture`, `route`, `plan`, `apply` on the atlas MCP server. Ingest runs in a knowledge base session, or in a project session against the project's knowledge base. The tools act on that one knowledge base either way; nothing here names a vault. A project session's capture records the project as provenance on its own. A project with no knowledge base cannot ingest: say so and hand off to `atlas-project`, which links one. ## Agree on scope 1. Call `status`, then `inbox`. `inbox` lists what waits in the knowledge base's inbox and whether each file is already captured. In a project session it also lists `notes`, the notes that wait to become threads: those are not sources; leave them to `thread-stub` and say so. A file whose frontmatter says `type: project-snapshot` is a project snapshot: leave it to `describe` and say so. 2. Infer the budget; do not ask for one. A batch of up to five files, or one source under about fifty pages, gets no question: read every source in full and file what it names. Above that, ask one thing, which files now, and take the first five when the user has no preference. The preview before `apply` is where the user sees the page count; a question before reading is not. 3.