otto-ingest-project-knowledgelisted

# Ingest project knowledge Turn an external evidence source into small, reviewable project-knowledge proposals. This skill is for focused ingestion after setup or onboarding, not for dumping an entire document into the repository. ## Workflow 1. Identify the source and its authority: user-confirmed decision, project document, measured test, Git change, or external research. If the source is ambiguous or untrusted, ask before recording. 2. Read `docs/project-knowledge.md` and query existing knowledge. Avoid creating a duplicate or weakening a confirmed page. 3. Extract only durable claims. Split unrelated claims into separate pages and classify factual knowledge as `decision`, `constraint`, `requirement`, or `architecture`. Treat a durable initiative as a project charter and an outside source with project relevance as a reference. 4. For each candidate, choose a readable kebab-case id and write focused rich Markdown compiled truth plus an evidence note that identifies the source. Use `[[wiki links]]` for meaningful relationships. Preserve relevant alternatives, rationale, and uncertainty in the evidence rather than presenting inference as fact. 5. Call `record_project_knowledge` for factual candidates, `record_project_charter` for initiatives, and `record_project_reference` for sources, leaving new pages `proposed`. For a claim that updates an existing page, use `update_project_knowledge_truth` with a reason instead of creating a second page. U