@hasna/knowledge 0.2.21 → 0.2.23

package/README.md

@@ -76,6 +76,11 @@ open-knowledge db init --scope project
 # Initialize scalable wiki/schema/index/log artifacts
 open-knowledge wiki init --scope project
 
+# Compile cited wiki pages, file approved answers, and lint wiki health
+open-knowledge wiki compile "handbook policy" --title "Handbook Policy" --scope project --json
+open-knowledge wiki file-answer "How do we cite policy?" --content "Use cited source context." --approve-write --scope project --json
+open-knowledge wiki lint --scope project --json
+
 # Ingest an open-files source manifest into the project SQLite catalog
 open-knowledge ingest manifest ./open-files-manifest.jsonl --scope project --json
 
@@ -237,11 +242,22 @@ Initialize or inspect the versioned SQLite catalog at
 ### wiki
 ```bash
 open-knowledge wiki init [--scope project]
+open-knowledge wiki compile [query|source-ref...] [--title <title>] [--limit <n>] [--scope project] [--json]
+open-knowledge wiki file-answer <prompt> --content <answer> [--approve-write] [--scope project] [--json]
+open-knowledge wiki lint [--scope project] [--json]
 ```
 Create starter generated-knowledge artifacts through the artifact store:
 `schemas/v1.md`, `indexes/root.md`, `wiki/README.md`, and a dated JSONL log
 partition.
 
+`wiki compile` turns existing source chunks into a cited Markdown page under
+`wiki/generated/`, updates `knowledge_indexes`, records citations and a concept
+backlink, and appends a JSONL log partition. `wiki file-answer` keeps answer
+filing as a dry run unless `--approve-write` is supplied, then writes a cited
+answer note under `wiki/answers/`. `wiki lint` checks generated pages for
+missing citations, stale citations, duplicate titles, orphan pages, unresolved
+source refs, contradiction markers, and new article candidates.
+
 ### source
 ```bash
 open-knowledge source resolve <source-ref> [--purpose knowledge_answer|knowledge_index] [--limit <n>] [--scope project] [--json]
@@ -402,19 +418,54 @@ location with `--store <path>`.
 open-knowledge-mcp
 ```
 
-The MCP server exposes item tools (`ok_add`, `ok_list`, `ok_get`, `ok_update`,
-`ok_delete`, `ok_archive`, `ok_restore`, `ok_upsert`, `ok_untag`,
-`ok_bulk_delete`, `ok_prune`, `ok_dedupe`, `ok_stats`, `ok_export`,
-`ok_import`, `ok_batch`), workspace/storage inspection (`ok_paths`,
-`ok_storage_status`), provider/embedding tools (`ok_provider_status`,
-`ok_provider_models`, `ok_embeddings_status`, `ok_embeddings_index`,
-`ok_semantic_search`), reindex tools (`ok_reindex_status`,
-`ok_reindex_enqueue`, `ok_reindex_embeddings`), hybrid retrieval (`ok_search`),
-and source-ref parsing/resolution (`ok_parse_source_ref`,
-`ok_resolve_source`). The `knowledge_search` MCP tool returns reranked citation
-context packs for agent prompts, and `knowledge_ask` runs the same prompt flow
-exposed by `open-knowledge ask`. `ok_web_search` exposes safety-gated provider
-web search to MCP clients.
+The stable agent-facing MCP tools are:
+
+- `knowledge_search`: return a reranked citation context pack.
+- `knowledge_ask`: answer with read-only local knowledge and optional AI SDK
+  generation.
+- `knowledge_build`: run the prompt flow and optionally file a cited wiki answer
+  when `approve_write=true`.
+- `knowledge_get`: read an item, indexed source, wiki page, run, index, or
+  decision by id.
+- `knowledge_ingest`: ingest an open-files/S3/file/web source ref or open-files
+  manifest into the derived catalog.
+- `knowledge_web_search`: run safety-gated provider-native web search.
+- `knowledge_lint`: lint generated wiki pages for citation/source issues.
+- `knowledge_run_status`: list recent runs or inspect one run ledger.
+- `knowledge_storage`: inspect the local/S3/hosted storage contract.
+- `knowledge_resolve_source`: resolve indexed source chunks through the
+  read-only source boundary.
+
+Compatibility and lower-level tools remain available with the `ok_*` prefix:
+item tools (`ok_add`, `ok_list`, `ok_get`, `ok_update`, `ok_delete`,
+`ok_archive`, `ok_restore`, `ok_upsert`, `ok_untag`, `ok_bulk_delete`,
+`ok_prune`, `ok_dedupe`, `ok_stats`, `ok_export`, `ok_import`, `ok_batch`),
+workspace/storage inspection (`ok_paths`, `ok_storage_status`), providers,
+embeddings, reindexing, hybrid search, source parsing/resolution, and
+`ok_web_search`.
+
+MCP also publishes project-scope JSON resources for agent inspection:
+
+- `knowledge://project/config`
+- `knowledge://project/storage`
+- `knowledge://project/schema`
+- `knowledge://project/sources`
+- `knowledge://project/open-files`
+- `knowledge://project/wiki/pages`
+- `knowledge://project/indexes`
+- `knowledge://project/runs`
+- `knowledge://project/decisions`
+- Templated reads:
+  `knowledge://project/items/{id}`,
+  `knowledge://project/sources/{id}`,
+  `knowledge://project/wiki/pages/{id}`,
+  `knowledge://project/indexes/{id}`,
+  `knowledge://project/runs/{id}`,
+  `knowledge://project/decisions/{id}`
+
+These resources expose compact metadata, derived chunks, generated wiki text,
+run ledgers, and citation evidence. They do not expose raw source bytes from
+`open-files`, local files, or S3.
 
 ## Source And Artifact Boundary