otto-project-knowledgelisted

# Otto project knowledge operations Use the daemon-owned project-knowledge tools as the only write path. The canonical store is Markdown, kept either in the repository under `.otto/knowledge` or host-local under the daemon's `$OTTO_HOME`, depending on how the project is configured. The tools are identical in both cases, and either way current truth and its provenance must be changed atomically by Otto rather than by editing files directly. ## Read - At task start, consult the automatically injected active-page catalog. Use `list_project_knowledge`, `read_project_knowledge`, or `read_project_knowledge_root` for pages relevant to the task before broad repository searches. - Use `query_project_knowledge` when the relevant page is not obvious. Normal reads return only confirmed active pages. Include inactive pages only for an explicit knowledge review. - Read compiled truth, evidence, tags, and the complete timeline. Treat `superseded` pages as history, not current guidance. - The optional `KNOWLEDGE.md` beside the store is on-demand project guidance. When it holds project-specific content the injected catalog names its actual path; read it before writing or managing Knowledge. Do not load it merely because a task reads existing Knowledge. Unlike record pages and the generated index, the project may edit or remove this file directly; baked-in behavior applies when it is absent. ## Write - Use `record_project_knowledge` for a new fact. Include one of `decision