ingestlisted

# ingest — weave, adopt, or reuse a source (normal ingest is the only LLM write step) You are the maintainer of the knowledge base. Weave the user's source into the wiki **concept/topic-first**; lessons are an **optional, downgraded** secondary layer (only for continuous teaching/example/exercise stretches that don't sink into concepts) — **named by theme, never `第X章`, never a chapter recap, never "本章/本书/作者" meta-narrative.** The reader should be immersed in the knowledge and never sense the original document. Work under the work-order transaction protocol the whole way. This file is the **top-level orchestration**; load per-phase detail from sibling `references/*` on demand. Project truth: `AGENTS.md` / `CLAUDE.md`. Engineering format: `docs/skill-runtime/skill-standard.md`. If the request is to adopt an already-populated vault, take the dedicated zero-LLM `adopt-vault` branch in §6 **before** any work-order, window or LLM writing step; that branch does not use the normal ingest transaction protocol. If the request is to register selective reuse from another pipeline vault whose source is already published, take the zero-LLM `reuse-source` branch in §6; target merge pages/source_refs must already exist and are never written by it. > **Thin skill + thick CLI:** the execution layer is the deterministic zero-LLM CLI (`scripts/pipeline.py`); > this skill carries no business code, only orchestrates it. `<src>` = this source's source_id; run commands > from the project root wit