@bodhi-ventures/aiocs 0.4.0 → 0.5.1

package/README.md

@@ -30,15 +30,15 @@ For testing or local overrides, set:
 
 ```bash
 npm install -g @bodhi-ventures/aiocs
-docs --version
-docs --help
+aiocs --version
+aiocs --help
 command -v aiocs-mcp
 ```
 
 Zero-install fallback:
 
 ```bash
-npx -y -p @bodhi-ventures/aiocs docs --version
+npx -y -p @bodhi-ventures/aiocs aiocs --version
 npx -y -p @bodhi-ventures/aiocs aiocs-mcp
 ```
 
@@ -54,12 +54,12 @@ pnpm dev:mcp
 For AI agents, prefer the root-level `--json` flag for one-shot commands:
 
 ```bash
-docs --json version
-docs --json doctor
-docs --json init --no-fetch
-docs --json source list
-docs --json search "maker flow" --source hyperliquid
-docs --json show 42
+aiocs --json version
+aiocs --json doctor
+aiocs --json init --no-fetch
+aiocs --json source list
+aiocs --json search "maker flow" --source hyperliquid
+aiocs --json show 42
 ```
 
 `--json` emits exactly one JSON document to stdout with this envelope:
@@ -127,21 +127,21 @@ The open-source repo bundles both web and git sources in `sources/`:
 
 Additional machine-local source specs belong in `~/.aiocs/sources`.
 
-`docs init` bootstraps both managed locations, so source behavior is the same regardless of
+`aiocs init` bootstraps both managed locations, so source behavior is the same regardless of
 whether a spec lives in the repo or in `~/.aiocs/sources`.
 
 Bootstrap managed sources in one command:
 
 ```bash
-docs init --no-fetch
-docs --json init --no-fetch
+aiocs init --no-fetch
+aiocs --json init --no-fetch
 ```
 
 Validate the machine before bootstrapping:
 
 ```bash
-docs doctor
-docs --json doctor
+aiocs doctor
+aiocs --json doctor
 ```
 
 ## Workflow
@@ -151,54 +151,54 @@ Register a source:
 ```bash
 mkdir -p ~/.aiocs/sources
 cp /path/to/source.yaml ~/.aiocs/sources/my-source.yaml
-docs source upsert ~/.aiocs/sources/my-source.yaml
-docs source upsert /path/to/source.yaml
-docs source list
+aiocs source upsert ~/.aiocs/sources/my-source.yaml
+aiocs source upsert /path/to/source.yaml
+aiocs source list
 ```
 
 Fetch and snapshot docs:
 
 ```bash
-docs refresh due hyperliquid
-docs snapshot list hyperliquid
-docs refresh due
+aiocs refresh due hyperliquid
+aiocs snapshot list hyperliquid
+aiocs refresh due
 ```
 
 Force fetch remains available for explicit maintenance:
 
 ```bash
-docs fetch hyperliquid
-docs fetch all
+aiocs fetch hyperliquid
+aiocs fetch all
 ```
 
 Link docs to a local project:
 
 ```bash
-docs project link /absolute/path/to/project hyperliquid lighter
-docs project unlink /absolute/path/to/project lighter
+aiocs project link /absolute/path/to/project hyperliquid lighter
+aiocs project unlink /absolute/path/to/project lighter
 ```
 
 Search and inspect results:
 
 ```bash
-docs search "maker flow" --source hyperliquid
-docs search "WebSocketTransport" --source nktkas-hyperliquid --path "src/**" --language typescript
-docs search "maker flow" --source hyperliquid --mode lexical
-docs search "maker flow" --source hyperliquid --mode hybrid
-docs search "maker flow" --source hyperliquid --mode semantic
-docs search "maker flow" --all
-docs search "maker flow" --source hyperliquid --limit 5 --offset 0
-docs show 42
-docs canary hyperliquid
-docs diff hyperliquid
-docs embeddings status
-docs embeddings backfill all
-docs embeddings run
-docs backup export /absolute/path/to/backup
-docs verify coverage hyperliquid /absolute/path/to/reference.md
+aiocs search "maker flow" --source hyperliquid
+aiocs search "WebSocketTransport" --source nktkas-hyperliquid --path "src/**" --language typescript
+aiocs search "maker flow" --source hyperliquid --mode lexical
+aiocs search "maker flow" --source hyperliquid --mode hybrid
+aiocs search "maker flow" --source hyperliquid --mode semantic
+aiocs search "maker flow" --all
+aiocs search "maker flow" --source hyperliquid --limit 5 --offset 0
+aiocs show 42
+aiocs canary hyperliquid
+aiocs diff hyperliquid
+aiocs embeddings status
+aiocs embeddings backfill all
+aiocs embeddings run
+aiocs backup export /absolute/path/to/backup
+aiocs verify coverage hyperliquid /absolute/path/to/reference.md
 ```
 
-When `docs search` runs inside a linked project, it automatically scopes to that project's linked sources unless `--source` or `--all` is provided.
+When `aiocs search` runs inside a linked project, it automatically scopes to that project's linked sources unless `--source` or `--all` is provided.
 
 For agents, the intended decision order is:
 
@@ -319,22 +319,22 @@ All one-shot commands support `--json`:
 Representative examples:
 
 ```bash
-docs --json doctor
-docs --json init --no-fetch
-docs --json source list
-docs --json source upsert sources/hyperliquid.yaml
-docs --json refresh due hyperliquid
-docs --json canary hyperliquid
-docs --json refresh due
-docs --json diff hyperliquid
-docs --json embeddings status
-docs --json embeddings backfill all
-docs --json embeddings clear hyperliquid
-docs --json embeddings run
-docs --json project link /absolute/path/to/project hyperliquid lighter
-docs --json snapshot list hyperliquid
-docs --json backup export /absolute/path/to/backup
-docs --json verify coverage hyperliquid /absolute/path/to/reference.md
+aiocs --json doctor
+aiocs --json init --no-fetch
+aiocs --json source list
+aiocs --json source upsert sources/hyperliquid.yaml
+aiocs --json refresh due hyperliquid
+aiocs --json canary hyperliquid
+aiocs --json refresh due
+aiocs --json diff hyperliquid
+aiocs --json embeddings status
+aiocs --json embeddings backfill all
+aiocs --json embeddings clear hyperliquid
+aiocs --json embeddings run
+aiocs --json project link /absolute/path/to/project hyperliquid lighter
+aiocs --json snapshot list hyperliquid
+aiocs --json backup export /absolute/path/to/backup
+aiocs --json verify coverage hyperliquid /absolute/path/to/reference.md
 ```
 
 For multi-result commands like `fetch`, `refresh due`, and `search`, `data` contains structured collections rather than line-by-line output:
@@ -361,7 +361,7 @@ For multi-result commands like `fetch`, `refresh due`, and `search`, `data` cont
 `aiocs` ships a first-class long-running refresh process:
 
 ```bash
-docs daemon
+aiocs daemon
 ```
 
 The daemon bootstraps source specs from the configured directories, refreshes due sources, sleeps for the configured interval, and repeats.
@@ -371,7 +371,7 @@ Configured source spec directories are treated as the daemon’s source of truth
 - if a managed source spec is removed from disk, the source is removed from the catalog on the next bootstrap
 - if `AIOCS_SOURCE_SPEC_DIRS` is explicitly set but resolves to missing or empty directories, the daemon fails fast instead of silently idling
 - due canaries run independently from full fetch schedules so drift is caught earlier than the next full snapshot refresh
-- daemon heartbeat state is persisted in the local catalog and surfaced through `docs doctor`
+- daemon heartbeat state is persisted in the local catalog and surfaced through `aiocs doctor`
 - queued embedding jobs are processed in the same daemon cycle after fetches complete
 
 Environment variables:
@@ -389,10 +389,10 @@ For local agents, the daemon keeps the shared catalog under `~/.aiocs` warm whil
 
 ### Daemon JSON mode
 
-`docs daemon --json` is intentionally different from one-shot commands. Because it is long-running, it emits one JSON event per line:
+`aiocs daemon --json` is intentionally different from one-shot commands. Because it is long-running, it emits one JSON event per line:
 
 ```bash
-docs --json daemon
+aiocs --json daemon
 ```
 
 Example event stream:
@@ -488,7 +488,7 @@ docker compose up --build -d
 
 The compose file:
 
-- runs `docs daemon` as the container entrypoint
+- runs `aiocs daemon` as the container entrypoint
 - bind-mounts `${HOME}/.aiocs` into `/root/.aiocs` so the container shares the same local catalog defaults as the host CLI
 - bind-mounts `./sources` into `/app/sources` so source spec edits are picked up without rebuilding
 - runs a dedicated `aiocs-qdrant` container for vector search

package/dist/{chunk-TSNV6PND.js → chunk-TSTOA3Q6.js}

@@ -3987,7 +3987,7 @@ async function startDaemon(input) {
 // package.json
 var package_default = {
   name: "@bodhi-ventures/aiocs",
-  version: "0.4.0",
+  version: "0.5.1",
   license: "MIT",
   type: "module",
   description: "Local-only documentation store, fetcher, and search CLI for AI agents.",
@@ -4020,7 +4020,7 @@ var package_default = {
     "skills"
   ],
   bin: {
-    docs: "./dist/cli.js",
+    aiocs: "./dist/cli.js",
     "aiocs-mcp": "./dist/mcp-server.js"
   },
   engines: {

package/dist/cli.js

@@ -31,7 +31,7 @@ import {
   unlinkProjectSources,
   upsertSourceFromSpecFile,
   verifyCoverage
-} from "./chunk-TSNV6PND.js";
+} from "./chunk-TSTOA3Q6.js";
 
 // src/cli.ts
 import { Command, CommanderError as CommanderError2 } from "commander";
@@ -245,7 +245,7 @@ function createDaemonLogger(json) {
   };
 }
 var program = new Command();
-program.name("docs").description("Local-only docs fetch and search CLI for AI agents.").option("-V, --version", "emit the current aiocs version").option("--json", "emit machine-readable JSON output").showHelpAfterError();
+program.name("aiocs").description("Local-only documentation fetch and search CLI for AI agents.").option("-V, --version", "emit the current aiocs version").option("--json", "emit machine-readable JSON output").showHelpAfterError();
 program.configureOutput({
   writeOut(output) {
     if (!argvWantsJson(process.argv)) {

package/dist/mcp-server.js

@@ -26,7 +26,7 @@ import {
   unlinkProjectSources,
   upsertSourceFromSpecFile,
   verifyCoverage
-} from "./chunk-TSNV6PND.js";
+} from "./chunk-TSTOA3Q6.js";
 
 // src/mcp-server.ts
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";

package/docs/codex-integration.md

@@ -8,22 +8,22 @@ Install the CLI and MCP binary globally:
 
 ```bash
 npm install -g @bodhi-ventures/aiocs
-docs --version
+aiocs --version
 command -v aiocs-mcp
 ```
 
 If global install is unavailable, use `npx` only as a fallback:
 
 ```bash
-npx -y -p @bodhi-ventures/aiocs docs --version
+npx -y -p @bodhi-ventures/aiocs aiocs --version
 npx -y -p @bodhi-ventures/aiocs aiocs-mcp
 ```
 
 The `aiocs-mcp` process is an MCP stdio server, so running it directly will wait for MCP clients instead of printing interactive help. The useful validation commands are:
 
 ```bash
-docs --json doctor
-docs --json init --no-fetch
+aiocs --json doctor
+aiocs --json init --no-fetch
 ```
 
 Register `aiocs-mcp` as a global Codex MCP server so the main agent can use it directly without shell fallback:
@@ -37,7 +37,7 @@ command = "aiocs-mcp"
 
 1. Prefer `aiocs` before live browsing when the requested docs may already exist locally.
 2. Prefer MCP through `aiocs-mcp` when Codex can use it.
-3. Fall back to `docs --json ...` only when MCP is unavailable.
+3. Fall back to `aiocs --json ...` only when MCP is unavailable.
 4. Check `source_list` before assuming a source is missing or stale.
 5. Default to `search mode=auto`.
 6. Use `mode=lexical` for exact identifiers, endpoint names, headings, and error strings.
@@ -65,7 +65,7 @@ Once those symlinks exist, Codex can load `aiocs` for normal local-doc lookup an
 ## Subagent options
 
 The repo ships a ready-to-copy specialist definition at
-[`agents/aiocs-docs-specialist.toml`](../agents/aiocs-docs-specialist.toml).
+[`agents/aiocs-specialist.toml`](../agents/aiocs-specialist.toml).
 
 It points at the globally installed `aiocs-mcp` binary so Codex uses the published package by default.
 
@@ -74,7 +74,7 @@ To expose that agent to Codex:
 ```bash
 AIOCS_REPO=/absolute/path/to/your/aiocs/checkout
 mkdir -p ~/.codex/agents
-ln -sfn "$AIOCS_REPO/agents/aiocs-docs-specialist.toml" ~/.codex/agents/aiocs-docs-specialist.toml
+ln -sfn "$AIOCS_REPO/agents/aiocs-specialist.toml" ~/.codex/agents/aiocs-specialist.toml
 ```
 
 ## Suggested Codex flows
@@ -82,17 +82,17 @@ ln -sfn "$AIOCS_REPO/agents/aiocs-docs-specialist.toml" ~/.codex/agents/aiocs-do
 Health and bootstrap:
 
 ```bash
-docs --json doctor
-docs --json init --no-fetch
+aiocs --json doctor
+aiocs --json init --no-fetch
 ```
 
-Local docs lookup:
+Local aiocs lookup:
 
 ```bash
-docs --json source list
-docs --json search "maker flow" --source hyperliquid --mode auto
-docs --json search "WebSocketTransport" --source nktkas-hyperliquid --path "src/**" --language typescript --mode lexical
-docs --json show 42
+aiocs --json source list
+aiocs --json search "maker flow" --source hyperliquid --mode auto
+aiocs --json search "WebSocketTransport" --source nktkas-hyperliquid --path "src/**" --language typescript --mode lexical
+aiocs --json show 42
 ```
 
 Missing or stale sources:
@@ -101,24 +101,24 @@ Missing or stale sources:
 # user-managed source specs live here
 ~/.aiocs/sources
 
-docs --json source upsert ~/.aiocs/sources/my-source.yaml
-docs --json refresh due my-source
+aiocs --json source upsert ~/.aiocs/sources/my-source.yaml
+aiocs --json refresh due my-source
 ```
 
 Drift, change, and completeness:
 
 ```bash
-docs --json canary hyperliquid
-docs --json diff hyperliquid
-docs --json verify coverage hyperliquid /absolute/path/to/reference.md
+aiocs --json canary hyperliquid
+aiocs --json diff hyperliquid
+aiocs --json verify coverage hyperliquid /absolute/path/to/reference.md
 ```
 
 Catalog maintenance:
 
 ```bash
-docs --json refresh due hyperliquid
-docs --json embeddings status
-docs --json backup export /absolute/path/to/backup
+aiocs --json refresh due hyperliquid
+aiocs --json embeddings status
+aiocs --json backup export /absolute/path/to/backup
 ```
 
 ## MCP-first guidance

package/docs/json-contract.md

@@ -470,7 +470,7 @@ Summary status values:
 
 ## Daemon event stream
 
-`docs daemon --json` is intentionally different because the process is long-running. It emits newline-delimited JSON events to stdout rather than a single envelope.
+`aiocs daemon --json` is intentionally different because the process is long-running. It emits newline-delimited JSON events to stdout rather than a single envelope.
 
 Current event types:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bodhi-ventures/aiocs",
-  "version": "0.4.0",
+  "version": "0.5.1",
   "license": "MIT",
   "type": "module",
   "description": "Local-only documentation store, fetcher, and search CLI for AI agents.",
@@ -33,7 +33,7 @@
     "skills"
   ],
   "bin": {
-    "docs": "./dist/cli.js",
+    "aiocs": "./dist/cli.js",
     "aiocs-mcp": "./dist/mcp-server.js"
   },
   "engines": {

package/skills/aiocs/SKILL.md

@@ -33,7 +33,7 @@ Use this skill when you need authoritative local documentation lookup through th
 1. Prefer `aiocs-mcp` when an MCP client can use it directly.
 2. Otherwise use the CLI with the root `--json` flag.
 3. Avoid parsing human-formatted CLI output unless there is no alternative.
-4. Assume `docs` and `aiocs-mcp` come from the globally installed `@bodhi-ventures/aiocs` package unless the user explicitly asks for a checkout-local development build.
+4. Assume `aiocs` and `aiocs-mcp` come from the globally installed `@bodhi-ventures/aiocs` package unless the user explicitly asks for a checkout-local development build.
 5. Use `npx -y -p @bodhi-ventures/aiocs ...` only as a fallback when the global install is unavailable.
 
 ## Search defaults for agents
@@ -50,13 +50,13 @@ Use this skill when you need authoritative local documentation lookup through th
 Validate the local runtime:
 
 ```bash
-docs --json doctor
+aiocs --json doctor
 ```
 
 Bootstrap managed sources from the repo bundle and `~/.aiocs/sources`:
 
 ```bash
-docs --json init --no-fetch
+aiocs --json init --no-fetch
 ```
 
 ## Core commands
@@ -64,51 +64,51 @@ docs --json init --no-fetch
 Search the shared catalog:
 
 ```bash
-docs --json search "maker flow" --source hyperliquid
-docs --json search "maker flow" --all
-docs --json search "maker flow" --source hyperliquid --limit 5 --offset 0
-docs --json search "maker flow" --source hyperliquid --mode hybrid
-docs --json search "WebSocketTransport" --source nktkas-hyperliquid --path "src/**" --language typescript --mode lexical
+aiocs --json search "maker flow" --source hyperliquid
+aiocs --json search "maker flow" --all
+aiocs --json search "maker flow" --source hyperliquid --limit 5 --offset 0
+aiocs --json search "maker flow" --source hyperliquid --mode hybrid
+aiocs --json search "WebSocketTransport" --source nktkas-hyperliquid --path "src/**" --language typescript --mode lexical
 ```
 
 Inspect a specific chunk:
 
 ```bash
-docs --json show 42
+aiocs --json show 42
 ```
 
 Inspect source availability and health:
 
 ```bash
-docs --json source list
-docs --json canary hyperliquid
-docs --json embeddings status
+aiocs --json source list
+aiocs --json canary hyperliquid
+aiocs --json embeddings status
 ```
 
 Inspect what changed between snapshots:
 
 ```bash
-docs --json diff hyperliquid
+aiocs --json diff hyperliquid
 ```
 
 Back up or restore the shared catalog:
 
 ```bash
-docs --json backup export /absolute/path/to/backup
-docs --json backup import /absolute/path/to/backup --replace-existing
+aiocs --json backup export /absolute/path/to/backup
+aiocs --json backup import /absolute/path/to/backup --replace-existing
 ```
 
 Verify fetched coverage against reference markdown:
 
 ```bash
-docs --json verify coverage hyperliquid /absolute/path/to/reference.md
+aiocs --json verify coverage hyperliquid /absolute/path/to/reference.md
 ```
 
 Scope docs to a project path:
 
 ```bash
-docs --json project link /absolute/path/to/project hyperliquid lighter
-docs --json project unlink /absolute/path/to/project lighter
+aiocs --json project link /absolute/path/to/project hyperliquid lighter
+aiocs --json project unlink /absolute/path/to/project lighter
 ```
 
 ## MCP tools
@@ -150,8 +150,8 @@ Mutation-capable MCP tools such as `source_upsert`, `refresh_due`, and `fetch` b
 
 - The catalog is local-only and shared across projects on the same machine.
 - Default state root: `~/.aiocs/data`, `~/.aiocs/config`, and `~/.aiocs/sources`.
-- Use `docs daemon` or the Docker daemon service when the catalog should stay fresh automatically.
-- `docs search --mode auto` is the right default for agents; it uses hybrid retrieval only when embeddings are current and healthy for the requested scope.
+- Use `aiocs daemon` or the Docker daemon service when the catalog should stay fresh automatically.
+- `aiocs search --mode auto` is the right default for agents; it uses hybrid retrieval only when embeddings are current and healthy for the requested scope.
 - The Docker Compose stack includes a dedicated `aiocs-qdrant` container and expects Ollama to be reachable separately.
 - Canaries are the first place to look when a docs site changed and fetches started degrading.
 - Newly added or changed sources become due immediately, so `refresh due <source-id>` is the safe first refresh path after upsert.

package/skills/aiocs-curation/SKILL.md

@@ -9,7 +9,7 @@ Use this skill when you need to add, refresh, repair, or otherwise mutate `aiocs
 
 ## When to use it
 
-- The requested docs source is missing from the local `aiocs` catalog and is worth curating for reuse.
+- The requested source is missing from the local `aiocs` catalog and is worth curating for reuse.
 - An existing source is stale and should be refreshed instead of bypassed.
 - A source spec needs to be created, updated, or upserted under `~/.aiocs/sources`.
 - A reusable external git repository should be added as a `kind: git` source under `~/.aiocs/sources`.
@@ -30,7 +30,7 @@ Use this skill when you need to add, refresh, repair, or otherwise mutate `aiocs
 
 1. Prefer `aiocs-mcp` when an MCP client can use it directly.
 2. Otherwise use the CLI with the root `--json` flag.
-3. Assume `docs` and `aiocs-mcp` come from the globally installed `@bodhi-ventures/aiocs` package unless the user explicitly asks for a checkout-local development build.
+3. Assume `aiocs` and `aiocs-mcp` come from the globally installed `@bodhi-ventures/aiocs` package unless the user explicitly asks for a checkout-local development build.
 4. Use `npx -y -p @bodhi-ventures/aiocs ...` only as a fallback when the global install is unavailable.
 
 ## User-managed sources
@@ -48,33 +48,33 @@ Create or update source specs there instead of editing the bundled repo sources.
 Validate the machine before curation:
 
 ```bash
-docs --json doctor
-docs --json source list
+aiocs --json doctor
+aiocs --json source list
 ```
 
 Add or update a machine-local source:
 
 ```bash
 mkdir -p ~/.aiocs/sources
-docs --json source upsert ~/.aiocs/sources/my-source.yaml
+aiocs --json source upsert ~/.aiocs/sources/my-source.yaml
 ```
 
 Refresh only what is needed:
 
 ```bash
-docs --json refresh due my-source
-docs --json refresh due hyperliquid
-docs --json refresh due nktkas-hyperliquid
-docs --json fetch my-source
-docs --json canary my-source
+aiocs --json refresh due my-source
+aiocs --json refresh due hyperliquid
+aiocs --json refresh due nktkas-hyperliquid
+aiocs --json fetch my-source
+aiocs --json canary my-source
 ```
 
 Heavy maintenance remains explicit:
 
 ```bash
-docs --json fetch all
-docs --json embeddings backfill all
-docs --json embeddings run
+aiocs --json fetch all
+aiocs --json embeddings backfill all
+aiocs --json embeddings run
 ```
 
 ## MCP tools