@hasna/knowledge 0.2.28 → 0.2.29

package/dist/index.js

@@ -5080,7 +5080,7 @@ function agentSchemaTemplate() {
 ## Source Rules
 
 - Treat open-files source references as the preferred source of truth.
-- Do not copy raw source files into open-knowledge.
+- Do not copy raw source files into knowledge.
 - Cite every durable fact with a source URI, revision/hash when available, and optional span.
 - Mark uncertainty explicitly when sources disagree or are incomplete.
 
@@ -5341,7 +5341,7 @@ class KnowledgeService {
       artifact_uri_prefix: storage.artifact_store.uri_prefix,
       canonical_hasna_xyz: storage.canonical_hasna_xyz,
       config_path: workspace.configPath,
-      next: mode === "hosted" ? ["open-knowledge auth login --api-key <key>", "open-knowledge storage status --json", "open-knowledge remote contracts --json"] : ["open-knowledge search <query>", "knowledge <prompt>"],
+      next: mode === "hosted" ? ["knowledge auth login --api-key <key>", "knowledge storage status --json", "knowledge remote contracts --json"] : ["knowledge search <query>", "knowledge <prompt>"],
       message: `Set knowledge mode to ${mode}`
     };
   }

package/docs/architecture/ai-native-knowledge-base.md

@@ -1,6 +1,6 @@
 # AI-Native Knowledge Base Architecture
 
-`open-knowledge` is the local-first knowledge engine for Hasna projects and
+`knowledge` is the local-first knowledge engine for Hasna projects and
 agents. It should make company knowledge durable, searchable, citable, and safe
 for agents to reuse. It is not the raw file bucket. Raw source bytes belong to
 `open-files`.
@@ -87,7 +87,7 @@ workspace they describe.
 
 ## Source References
 
-`open-knowledge` stores references, not raw source bytes. Supported source ref
+`knowledge` stores references, not raw source bytes. Supported source ref
 forms:
 
 ```text
@@ -124,8 +124,8 @@ without reconstructing it later.
 The local resolver is exposed through:
 
 ```bash
-open-knowledge source resolve <source-ref> --purpose knowledge_answer --json
-open-knowledge ingest source <source-ref> --purpose knowledge_index --json
+knowledge source resolve <source-ref> --purpose knowledge_answer --json
+knowledge ingest source <source-ref> --purpose knowledge_index --json
 ```
 
 and the MCP tool `ok_resolve_source`. It reads the knowledge catalog only,
@@ -169,7 +169,7 @@ s3://hasna-xyz-opensource-knowledge-prod/.hasna/apps/knowledge/
 The app config can be materialized with:
 
 ```bash
-open-knowledge setup --mode hosted --canonical-hasna-xyz --scope project --json
+knowledge setup --mode hosted --canonical-hasna-xyz --scope project --json
 ```
 
 The canonical metadata-only secret paths are:
@@ -190,7 +190,7 @@ run outputs.
 The storage contract is inspectable through:
 
 ```bash
-open-knowledge storage status --scope project --json
+knowledge storage status --scope project --json
 ```
 
 That contract names the local app path, SQLite catalog, generated artifact
@@ -251,7 +251,7 @@ new-article candidates.
 Search is hybrid:
 
 1. `open-files` supplies source manifests, revisions, hashes, and extracted text.
-2. `open-knowledge` chunks extracted text and generated wiki pages.
+2. `knowledge` chunks extracted text and generated wiki pages.
 3. Chunks and pages are indexed with keyword search and embeddings.
 4. Queries run through keyword FTS, vector search, and wiki/citation graph
    expansion.
@@ -263,14 +263,14 @@ mode can use Postgres with pgvector or a managed vector index. Permission
 filters must be applied before agent context is assembled.
 
 The first local semantic-search implementation indexes derived chunks with
-`open-knowledge embeddings index` and queries them with
-`open-knowledge search --semantic` or the lower-level
-`open-knowledge embeddings search`. It stores OpenAI embedding vectors as
+`knowledge embeddings index` and queries them with
+`knowledge search --semantic` or the lower-level
+`knowledge embeddings search`. It stores OpenAI embedding vectors as
 generated metadata rows, not raw source bytes, and pins each row to `open-files`
 provenance: source ref/URI, revision/hash, chunk offsets, token count, provider,
 model, dimensions, status, and timestamps. The structured `search` contract
 merges keyword FTS, wiki/index catalog hits, generated wiki chunks, and optional
-vector results. `open-knowledge search --context` and MCP `knowledge_search`
+vector results. `knowledge search --context` and MCP `knowledge_search`
 turn those rows into reranked citation context packs with selected excerpts,
 freshness and permission notes, graph evidence, and final rerank scores. The
 local SQLite index can later move to pgvector or a managed hosted vector store
@@ -291,7 +291,7 @@ These resources expose derived chunks, generated wiki artifacts, citations, run
 ledgers, and storage/index metadata without exposing raw source bytes.
 
 Index freshness is explicit. `reindex_queue` tracks missing or stale embedding
-work, `open-knowledge reindex status|enqueue|embeddings` operates the local
+work, `knowledge reindex status|enqueue|embeddings` operates the local
 queue, and MCP exposes the same controls through `ok_reindex_status`,
 `ok_reindex_enqueue`, and `ok_reindex_embeddings`. Hosted mode can map the same
 contract to worker queues, S3/object artifact sync, Postgres/pgvector, or a
@@ -317,14 +317,14 @@ The command should:
 7. Record a run ledger with tool calls, sources, costs, outputs, and generated
    records.
 
-The first implementation exposes this as `open-knowledge ask|build <prompt>`
+The first implementation exposes this as `knowledge ask|build <prompt>`
 and the installed `knowledge <prompt>` bin alias. It retrieves read-only context,
 returns a local citation draft by default, optionally calls AI SDK generation via
 `--generate`, records `runs`, `run_events`, and `provider_usage`, and only
 proposes durable wiki updates until the wiki compile/write task owns writes.
 
 Provider-native web search is exposed separately as
-`open-knowledge web search <query>` and MCP `ok_web_search`. Real network access
+`knowledge web search <query>` and MCP `ok_web_search`. Real network access
 is safety-gated; OpenAI and Anthropic use provider web-search tools through AI
 SDK, while DeepSeek remains a future fallback/external-search path. Returned web
 snippets can optionally be filed as read-only `web` source refs for later local
@@ -340,14 +340,14 @@ AI provider setup is BYOK and AI SDK v6 based. The local provider layer tracks:
 - DeepSeek via `@ai-sdk/deepseek`, defaulting to `deepseek:deepseek-chat`.
 
 Model aliases live in config and can be inspected with
-`open-knowledge providers models`. Credentials are resolved from env vars by
+`knowledge providers models`. Credentials are resolved from env vars by
 default, checked without making provider calls, and usage can be normalized into
 the existing `provider_usage` table for future prompt, embedding, and web-search
 runs.
 
 ## Non-Goals
 
-- Do not make `open-knowledge` own raw source files.
+- Do not make `knowledge` own raw source files.
 - Do not make hosted account, billing, worker, or tenant state required for local
   use.
 - Do not let semantic search bypass permissions.

package/docs/architecture/hosted-wrapper-responsibilities.md

@@ -1,6 +1,6 @@
 # Hosted Wrapper Responsibilities
 
-`open-knowledge` stays local-first and open source. A future hosted/SaaS wrapper
+`knowledge` stays local-first and open source. A future hosted/SaaS wrapper
 can implement remote APIs around the same contracts, but tenant state,
 infrastructure ownership, and commercial controls must live outside this
 package.
@@ -30,7 +30,7 @@ The hosted wrapper owns:
 
 Local mode must not require hosted identity, billing, queue workers, or hosted
 object storage. Hosted mode is an explicit remote boundary selected through
-`open-knowledge setup --mode hosted` plus `KNOWLEDGE_API_URL` and
+`knowledge setup --mode hosted` plus `KNOWLEDGE_API_URL` and
 `KNOWLEDGE_API_KEY`.
 
 ## Identity And Access
@@ -66,9 +66,9 @@ should own connector orchestration and source sync:
 - Source snapshots, immutable object ids, revisions, hashes, MIME metadata,
   extracted text refs, ACL metadata, and change outboxes.
 - Read-only resolver APIs that expose derived extracted text or allowed chunks
-  to `open-knowledge` without exposing storage credentials.
+  to `knowledge` without exposing storage credentials.
 
-`open-knowledge` should continue to consume manifests, source refs, and outbox
+`knowledge` should continue to consume manifests, source refs, and outbox
 events. It should not own connector credentials or raw source object lifecycle.
 
 ## Storage And Secrets
@@ -120,7 +120,7 @@ revision, artifact hash, or run id where possible.
 The wrapper should implement the contract printed by:
 
 ```bash
-open-knowledge remote contracts --scope project --json
+knowledge remote contracts --scope project --json
 ```
 
 Required endpoint families:

package/docs/architecture/hybrid-semantic-search.md

@@ -1,6 +1,6 @@
 # Hybrid Semantic Search Architecture
 
-`open-knowledge` search is hybrid by design. Keyword search, semantic vector
+`knowledge` search is hybrid by design. Keyword search, semantic vector
 search, wiki graph traversal, and citation/provenance signals each solve a
 different part of the retrieval problem.
 
@@ -15,7 +15,7 @@ different part of the retrieval problem.
 - Read-only content resolution for deeper reads.
 - Change events that trigger incremental reindexing.
 
-`open-knowledge` owns:
+`knowledge` owns:
 
 - Chunk boundaries and chunk metadata.
 - Embeddings for source chunks, wiki pages, decisions, and durable answers.
@@ -49,13 +49,13 @@ contracts.
 The current local command surface is:
 
 ```bash
-open-knowledge search "company wiki policy" --scope project --json
-open-knowledge search "company wiki policy" --scope project --semantic --json
-open-knowledge search "company wiki policy" --scope project --context --json
-open-knowledge reindex status --scope project --json
-open-knowledge reindex embeddings --scope project --fake --json
-open-knowledge embeddings index --scope project --model openai:text-embedding-3-small
-open-knowledge embeddings search "company wiki policy" --scope project --json
+knowledge search "company wiki policy" --scope project --json
+knowledge search "company wiki policy" --scope project --semantic --json
+knowledge search "company wiki policy" --scope project --context --json
+knowledge reindex status --scope project --json
+knowledge reindex embeddings --scope project --fake --json
+knowledge embeddings index --scope project --model openai:text-embedding-3-small
+knowledge embeddings search "company wiki policy" --scope project --json
 ```
 
 `search` is the structured hybrid layer for agents. `embeddings search` is the
@@ -139,15 +139,15 @@ They should receive context packs:
 This keeps agent prompts stable while the retrieval internals evolve.
 
 The local context-pack implementation is available through
-`open-knowledge search --context` and MCP `knowledge_search`. It reranks merged
+`knowledge search --context` and MCP `knowledge_search`. It reranks merged
 search rows using exact-term coverage, citation availability, source freshness,
 and source/wiki authority, then emits excerpts and citation objects that preserve
 source refs, artifact URIs, revision/hash metadata, offsets, and provenance.
-`open-knowledge ask|build <prompt>`, the installed `knowledge <prompt>` alias,
+`knowledge ask|build <prompt>`, the installed `knowledge <prompt>` alias,
 and MCP `knowledge_ask|knowledge_build` wrap this context pack in a run ledger
 and return a citation draft or explicit AI SDK generated answer.
 
-Provider-native web search lives beside local retrieval. `open-knowledge web
+Provider-native web search lives beside local retrieval. `knowledge web
 search` and MCP `knowledge_web_search` are safety-gated, capture provider
 sources, and can file snippets as read-only `web` source refs so later local
 retrieval treats them like other cited sources. The lower-level `ok_web_search`

package/docs/canonical-secrets-bootstrap-2026-06-08.md

@@ -61,7 +61,7 @@ hasna/xyz/opensource/knowledge/prod/s3
 
 Meaning:
 
-- `env`: open-knowledge production app config metadata.
+- `env`: knowledge production app config metadata.
 - `aws`: AWS account/profile/region and related app config metadata.
 - `s3`: canonical app storage bucket metadata for
   `hasna-xyz-opensource-knowledge-prod`.

package/docs/examples/company-wiki-workflow.md

@@ -1,14 +1,14 @@
 # Company Wiki Workflow
 
-This workflow shows how to use `open-knowledge` as an AI-native company wiki
+This workflow shows how to use `knowledge` as an AI-native company wiki
 layer over source files owned by `open-files`.
 
 ## 1. Initialize The Project Workspace
 
 ```bash
-open-knowledge paths --scope project --json
-open-knowledge db init --scope project --json
-open-knowledge wiki init --scope project --json
+knowledge paths --scope project --json
+knowledge db init --scope project --json
+knowledge wiki init --scope project --json
 ```
 
 Project state is created under:
@@ -50,7 +50,7 @@ and extracted text:
 Then ingest it:
 
 ```bash
-open-knowledge ingest manifest ./open-files-manifest.jsonl --scope project --json
+knowledge ingest manifest ./open-files-manifest.jsonl --scope project --json
 ```
 
 The knowledge app stores source refs, revisions, redacted chunks, offsets, and
@@ -61,20 +61,20 @@ citations. It does not store raw source bytes or connector credentials.
 Run local keyword/catalog search first:
 
 ```bash
-open-knowledge search "expense policy" --scope project --json
+knowledge search "expense policy" --scope project --json
 ```
 
 Add deterministic local semantic indexing for a smoke test:
 
 ```bash
-open-knowledge embeddings index --scope project --fake --dimensions 8 --json
-open-knowledge search "expense policy" --scope project --semantic --fake --dimensions 8 --json
+knowledge embeddings index --scope project --fake --dimensions 8 --json
+knowledge search "expense policy" --scope project --semantic --fake --dimensions 8 --json
 ```
 
 Ask for an agent-ready context pack:
 
 ```bash
-open-knowledge search "expense policy" --scope project --context --json
+knowledge search "expense policy" --scope project --context --json
 ```
 
 ## 4. Answer With Citations
@@ -104,7 +104,7 @@ citations, and proposed wiki updates.
 Compile a cited page from indexed chunks:
 
 ```bash
-open-knowledge wiki compile "expense policy" \
+knowledge wiki compile "expense policy" \
   --title "Expense Policy" \
   --scope project \
   --json
@@ -113,7 +113,7 @@ open-knowledge wiki compile "expense policy" \
 File an approved answer note:
 
 ```bash
-open-knowledge wiki file-answer "How do we approve expenses?" \
+knowledge wiki file-answer "How do we approve expenses?" \
   --content "Use manager approval and cite the policy source." \
   --approve-write \
   --scope project \
@@ -123,7 +123,7 @@ open-knowledge wiki file-answer "How do we approve expenses?" \
 Lint the generated wiki:
 
 ```bash
-open-knowledge wiki lint --scope project --json
+knowledge wiki lint --scope project --json
 ```
 
 Generated pages are written through the artifact store and cataloged in
@@ -135,9 +135,9 @@ Markdown file.
 Consume open-files outbox events after source changes:
 
 ```bash
-open-knowledge reindex outbox ./open-files-outbox.jsonl --scope project --json
-open-knowledge reindex enqueue --scope project --json
-open-knowledge reindex embeddings --scope project --fake --dimensions 8 --json
+knowledge reindex outbox ./open-files-outbox.jsonl --scope project --json
+knowledge reindex enqueue --scope project --json
+knowledge reindex embeddings --scope project --fake --dimensions 8 --json
 ```
 
 This invalidates stale source chunks and refreshes embeddings without losing the
@@ -148,13 +148,13 @@ source refs and citation provenance.
 Run MCP over stdio:
 
 ```bash
-open-knowledge-mcp
+knowledge-mcp
 ```
 
 Or run local Streamable HTTP:
 
 ```bash
-open-knowledge-mcp --http --port 8819
+knowledge-mcp --http --port 8819
 ```
 
 Agents should prefer stable tools such as `knowledge_search`, `knowledge_ask`,
@@ -168,8 +168,8 @@ Agents should prefer stable tools such as `knowledge_search`, `knowledge_ask`,
 Hosted mode is only a remote client boundary:
 
 ```bash
-open-knowledge setup --mode hosted --api-url https://knowledge.hasna.xyz --scope project --json
-open-knowledge remote contracts --scope project --json
+knowledge setup --mode hosted --api-url https://knowledge.hasna.xyz --scope project --json
+knowledge remote contracts --scope project --json
 ```
 
 Generated artifacts may use S3 when configured, but raw source files still stay

package/docs/migration/json-to-sqlite.md

@@ -1,6 +1,6 @@
 # JSON To SQLite Migration
 
-`open-knowledge` began as a simple JSON note store. Current project mode uses a
+`knowledge` began as a simple JSON note store. Current project mode uses a
 Hasna app workspace and a versioned SQLite catalog:
 
 ```text
@@ -54,20 +54,20 @@ recorded correctly.
 Initialize the project catalog:
 
 ```bash
-open-knowledge db init --scope project --json
-open-knowledge wiki init --scope project --json
+knowledge db init --scope project --json
+knowledge wiki init --scope project --json
 ```
 
 Import open-files manifests:
 
 ```bash
-open-knowledge ingest manifest ./open-files-manifest.jsonl --scope project --json
+knowledge ingest manifest ./open-files-manifest.jsonl --scope project --json
 ```
 
 Import one allowed source ref:
 
 ```bash
-open-knowledge ingest source file:///absolute/path/to/handbook.md \
+knowledge ingest source file:///absolute/path/to/handbook.md \
   --purpose knowledge_index \
   --scope project \
   --json
@@ -76,7 +76,7 @@ open-knowledge ingest source file:///absolute/path/to/handbook.md \
 Resolve indexed source evidence:
 
 ```bash
-open-knowledge source resolve open-files://file/file_123/revision/rev_456 \
+knowledge source resolve open-files://file/file_123/revision/rev_456 \
   --purpose knowledge_answer \
   --scope project \
   --json
@@ -85,16 +85,16 @@ open-knowledge source resolve open-files://file/file_123/revision/rev_456 \
 ## Recommended Migration Path
 
 1. Keep the legacy JSON note store as an exportable compatibility layer.
-2. Run `open-knowledge paths --scope project --json` and confirm the project
+2. Run `knowledge paths --scope project --json` and confirm the project
    workspace is `.hasna/apps/knowledge`.
-3. Initialize `knowledge.db` with `open-knowledge db init --scope project`.
+3. Initialize `knowledge.db` with `knowledge db init --scope project`.
 4. Ingest source manifests from `open-files` rather than copying raw files into
-   `open-knowledge`.
-5. Run `open-knowledge search --scope project --json` to verify source chunks.
-6. Run `open-knowledge wiki compile` for durable cited pages.
-7. Run `open-knowledge wiki lint --scope project --json` before treating pages
+   `knowledge`.
+5. Run `knowledge search --scope project --json` to verify source chunks.
+6. Run `knowledge wiki compile` for durable cited pages.
+7. Run `knowledge wiki lint --scope project --json` before treating pages
    as company knowledge.
-8. Use `open-knowledge export --format jsonl` if legacy notes need to be
+8. Use `knowledge export --format jsonl` if legacy notes need to be
    archived or transformed outside the app.
 
 ## JSON Output Contracts
@@ -122,7 +122,7 @@ when successful and command-specific fields such as:
 ```bash
 HASNA_KNOWLEDGE_ALLOW_S3_READS=1 \
 HASNA_KNOWLEDGE_ALLOWED_S3_BUCKETS=my-bucket \
-open-knowledge ingest manifest s3://my-bucket/path/manifest.jsonl \
+knowledge ingest manifest s3://my-bucket/path/manifest.jsonl \
   --scope project \
   --json
 ```
@@ -131,7 +131,7 @@ open-knowledge ingest manifest s3://my-bucket/path/manifest.jsonl \
 
 ```bash
 HASNA_KNOWLEDGE_WEB_SEARCH=1 \
-open-knowledge web search "current policy source" --provider openai --json
+knowledge web search "current policy source" --provider openai --json
 ```
 
 - Use `--approve-write` only when a generated wiki artifact should be durable.
@@ -142,8 +142,8 @@ Hosted mode should not change local migration semantics. It only records a
 remote API boundary:
 
 ```bash
-open-knowledge setup --mode hosted --api-url https://knowledge.hasna.xyz --scope project --json
-open-knowledge remote contracts --scope project --json
+knowledge setup --mode hosted --api-url https://knowledge.hasna.xyz --scope project --json
+knowledge remote contracts --scope project --json
 ```
 
 A SaaS wrapper can later sync generated artifacts, run jobs, enforce tenant ACLs,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hasna/knowledge",
-  "version": "0.2.28",
+  "version": "0.2.29",
   "description": "Agent-friendly local knowledge CLI with JSON output, pagination, and safe destructive actions",
   "type": "module",
   "exports": {
@@ -12,9 +12,8 @@
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "bin": {
-    "knowledge": "bin/open-knowledge.js",
-    "open-knowledge": "bin/open-knowledge.js",
-    "open-knowledge-mcp": "bin/open-knowledge-mcp.js"
+    "knowledge": "bin/knowledge.js",
+    "knowledge-mcp": "bin/knowledge-mcp.js"
   },
   "files": [
     "bin",
@@ -26,7 +25,7 @@
   "scripts": {
     "test": "bun test",
     "test:cli": "bun test tests/cli.test.ts",
-    "build": "rm -rf dist && bun build --target=bun --outfile=bin/open-knowledge.js --minify --external @aws-sdk/client-s3 --external @aws-sdk/credential-providers --external ai --external @ai-sdk/openai --external @ai-sdk/anthropic --external @ai-sdk/deepseek src/cli.ts && bun build --target=bun --outfile=bin/open-knowledge-mcp.js --external @modelcontextprotocol/sdk --external @aws-sdk/client-s3 --external @aws-sdk/credential-providers --external ai --external @ai-sdk/openai --external @ai-sdk/anthropic --external @ai-sdk/deepseek src/mcp.js && bun build ./src/index.ts --outdir ./dist --target bun --external @aws-sdk/client-s3 --external @aws-sdk/credential-providers --external ai --external @ai-sdk/openai --external @ai-sdk/anthropic --external @ai-sdk/deepseek && bunx tsc -p tsconfig.build.json",
+    "build": "rm -rf dist && bun build --target=bun --outfile=bin/knowledge.js --minify --external @aws-sdk/client-s3 --external @aws-sdk/credential-providers --external ai --external @ai-sdk/openai --external @ai-sdk/anthropic --external @ai-sdk/deepseek src/cli.ts && bun build --target=bun --outfile=bin/knowledge-mcp.js --external @modelcontextprotocol/sdk --external @aws-sdk/client-s3 --external @aws-sdk/credential-providers --external ai --external @ai-sdk/openai --external @ai-sdk/anthropic --external @ai-sdk/deepseek src/mcp.js && bun build ./src/index.ts --outdir ./dist --target bun --external @aws-sdk/client-s3 --external @aws-sdk/credential-providers --external ai --external @ai-sdk/openai --external @ai-sdk/anthropic --external @ai-sdk/deepseek && bunx tsc -p tsconfig.build.json",
     "prepublishOnly": "bun run build"
   },
   "keywords": [