@bodhi-ventures/aiocs 0.3.1 → 0.5.0

package/skills/aiocs/SKILL.md

@@ -12,8 +12,6 @@ Use this skill when you need authoritative local documentation lookup through th
 - The user is asking about exchange or product docs that may already exist in the local `aiocs` catalog.
 - You need authoritative local docs for an exchange, SDK, or product without browsing the live site every time.
 - You need reusable reference search over a curated external git repository that already lives in `aiocs`.
-- You need to read from a compiled `aiocs` workspace wiki or inspect derived workspace artifacts.
-- You need to inspect workspace status, queued compile health, or raw ingested evidence before deciding whether curation is needed.
 - You want machine-readable search/show/diff/coverage results for an AI agent.
 - You need hybrid docs retrieval with lexical plus semantic/vector recall.
 - You need to validate runtime health before relying on the local docs catalog.
@@ -52,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
@@ -66,63 +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
-```
-
-Search or inspect a compiled workspace:
-
-```bash
-docs --json workspace status market-structure
-docs --json workspace search market-structure "transport design" --scope mixed
-docs --json workspace ingest list market-structure
-docs --json workspace ingest search market-structure "fee tier"
-docs --json workspace artifact list market-structure
-docs --json workspace artifact show market-structure derived/index.md
-docs --json workspace lint market-structure
+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
@@ -146,15 +132,6 @@ The `aiocs-mcp` server exposes the same core operations without shell parsing:
 - `backup_import`
 - `search`
 - `show`
-- `workspace_list`
-- `workspace_status`
-- `workspace_search`
-- `workspace_ingest_list`
-- `workspace_ingest_show`
-- `workspace_ingest_search`
-- `workspace_artifact_list`
-- `workspace_artifact_show`
-- `workspace_lint`
 - `verify_coverage`
 - `batch`
 
@@ -165,19 +142,17 @@ Mutation-capable MCP tools such as `source_upsert`, `refresh_due`, and `fetch` b
 1. If runtime health is in doubt, run `doctor`.
 2. Run `source_list` to see whether the source already exists.
 3. Use `search` in `auto` mode first, then `show` for the selected chunk.
-4. If the user is asking against a compiled research wiki, prefer `workspace_search` and `workspace_artifact_show`.
-5. Use `canary`, `diff_snapshots`, or `verify_coverage` when the question is about drift, changes, or completeness.
-6. If the source is missing or stale and the next step is to mutate `aiocs`, load `aiocs-curation`.
-7. Use `batch` when combining list/search/show or diff/coverage checks in one pass.
+4. Use `canary`, `diff_snapshots`, or `verify_coverage` when the question is about drift, changes, or completeness.
+5. If the source is missing or stale and the next step is to mutate `aiocs`, load `aiocs-curation`.
+6. Use `batch` when combining list/search/show or diff/coverage checks in one pass.
 
 ## Operational notes
 
 - 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.
-- Compiled research workspaces use LM Studio as the v1 compiler backend and expect `google/gemma-4-26b-a4b` to be loaded unless the environment overrides it.
 - 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.
 - CLI failures expose machine-readable `error.code` fields in `--json` mode.

package/skills/aiocs-curation/SKILL.md

@@ -9,13 +9,11 @@ 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`.
 - A canary is failing and the source needs remediation or targeted refetch.
-- A research workspace needs to be created, rebound, compiled, or asked to generate a report/slide artifact.
-- A workspace needs raw evidence ingest, auto-compile setup, queued compile processing, or Obsidian sync.
 - The user explicitly wants `aiocs` maintenance, source onboarding, or catalog repair.
 
 ## Trigger guidance for Codex
@@ -50,51 +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
-```
-
-Compile or regenerate a workspace wiki:
-
-```bash
-docs --json workspace create market-structure --label "Market Structure"
-docs --json workspace bind market-structure hyperliquid nktkas-hyperliquid
-docs --json workspace compile market-structure
-docs --json workspace configure market-structure --auto-compile true
-docs --json workspace queue-run
-docs --json workspace ingest add market-structure markdown-dir /absolute/path/to/notes --label "Research notes"
-docs --json workspace ingest add market-structure csv /absolute/path/to/fills.csv --label "Fills CSV"
-docs --json workspace ingest add market-structure json /absolute/path/to/manifest.json --label "Research manifest"
-docs --json workspace ingest add market-structure jsonl /absolute/path/to/events.jsonl --label "Events JSONL"
-docs --json workspace output market-structure report --name weekly-brief
-docs --json workspace output market-structure slides --name weekly-brief
-docs --json workspace answer market-structure note "What changed?" --name quick-note
-docs --json workspace sync obsidian market-structure /absolute/path/to/vault
+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
@@ -111,17 +91,6 @@ The `aiocs-mcp` server exposes the same curation operations without shell parsin
 - `embeddings_backfill`
 - `embeddings_clear`
 - `embeddings_run`
-- `workspace_create`
-- `workspace_bind`
-- `workspace_unbind`
-- `workspace_update`
-- `workspace_compile`
-- `workspace_queue_run`
-- `workspace_ingest_add`
-- `workspace_ingest_remove`
-- `workspace_output`
-- `workspace_answer`
-- `workspace_sync_obsidian`
 - `batch`
 
 ## Recommended Codex workflow
@@ -131,10 +100,7 @@ The `aiocs-mcp` server exposes the same curation operations without shell parsin
 3. If the source is missing but worth curating, create a spec under `~/.aiocs/sources`, then `source_upsert` it.
 4. After upsert, use `refresh due <source-id>` as the safe first fetch path.
 5. Use `canary` when the site changed or extraction drift is suspected.
-6. For research workspaces, bind curated sources and/or ingest raw evidence, then run `workspace compile`.
-7. Use `workspace output` and `workspace answer` only after a successful compile so outputs have source-backed provenance.
-8. Prefer `autoCompileEnabled` plus targeted queue processing over broad global rebuilds.
-9. Escalate to `fetch <source-id>` or `fetch all` only for explicit maintenance or when due-based refresh is not enough.
+6. Escalate to `fetch <source-id>` or `fetch all` only for explicit maintenance or when due-based refresh is not enough.
 
 ## Operational notes
 
@@ -142,4 +108,3 @@ The `aiocs-mcp` server exposes the same curation operations without shell parsin
 - `~/.aiocs/sources` and bundled repo sources behave the same once bootstrapped into the catalog.
 - Targeted refresh is the default. Broad refresh is a maintenance task, not a normal answering step.
 - Use `aiocs` for read/search flows and this skill only for catalog mutation.
-- Workspace compilation uses LM Studio and expects the configured model to be loaded before `workspace compile`, `workspace output`, or `workspace answer`.