@hasna/knowledge 0.2.8 → 0.2.10

package/README.md

@@ -11,6 +11,11 @@ engine for AI agents. It stores simple knowledge items today, creates a Hasna
 project workspace under `.hasna/apps/knowledge`, initializes a versioned
 `knowledge.db`, writes generated wiki artifacts, and exposes a stdio MCP server.
 
+CLI and MCP workspace operations share a `KnowledgeService` facade for config,
+safety policy, artifact storage, DB/wiki setup, source ingestion, source
+resolution, and outbox consumption. That keeps local project mode and future
+remote/S3-backed wrappers on the same service contracts.
+
 ## Install
 
 ```bash
@@ -66,6 +71,9 @@ open-knowledge wiki init --scope project
 # Ingest an open-files source manifest into the project SQLite catalog
 open-knowledge ingest manifest ./open-files-manifest.jsonl --scope project --json
 
+# Ingest one read-only source ref directly
+open-knowledge ingest source file:///absolute/path/to/handbook.md --purpose knowledge_index --scope project --json
+
 # Consume open-files change events and invalidate stale source chunks
 open-knowledge reindex outbox ./open-files-outbox.jsonl --scope project --json
 
@@ -184,11 +192,20 @@ raw source retrieval remains owned by `open-files`.
 ### ingest
 ```bash
 open-knowledge ingest manifest <file|s3://bucket/key> [--scope project] [--json]
+open-knowledge ingest source <source-ref> [--purpose knowledge_index] [--scope project] [--json]
 ```
 Import an open-files JSON or JSONL source manifest into `knowledge.db`. This
 upserts sources and source revisions, stores hash/MIME/status/permission
 metadata, and chunks embedded extracted text when the manifest includes it.
 
+`ingest source` accepts `open-files://`, `file://`, `s3://`, and `https://`
+refs. It reads source content through a read-only boundary, redacts known
+secrets before storage, records hashes/revisions, and stores only derived chunks
+and citation spans. Web and S3 reads remain opt-in through the safety policy.
+For `open-files://` refs, the source must already be present in the local
+knowledge catalog through a manifest or extracted-text ref until the open-files
+resolver API lands.
+
 ### reindex
 ```bash
 open-knowledge reindex outbox <file|s3://bucket/key> [--scope project] [--json]
@@ -259,6 +276,11 @@ only the indexed, derived knowledge catalog. The resolver enforces read-only
 purpose labels from source permissions, returns chunk citation evidence, writes
 an audit event, and keeps bytes/storage credentials inside `open-files`.
 
+`open-knowledge ingest source` can also build derived chunks from an allowed
+source ref. It does not copy raw files into the knowledge workspace; local file,
+S3, web, and open-files inputs are converted into redacted chunks with offsets,
+hashes, revision metadata, and FTS rows.
+
 Generated knowledge artifacts can be stored locally under
 `.hasna/apps/knowledge/artifacts` or through the S3 artifact-store adapter.