@yugabytedb/meko-mcp 1.2.0 → 2.0.0

package/assets/skills/meko-mcp-tools/references/tools-overview.md

@@ -1,62 +1,40 @@
 # Complete Tool Catalog and Decision Tree
 
-**26 tools on cloud Meko** (verified against `https://mcp.mekodata.ai/mcp` on 2026-05-07). Earlier counts of 25 or 31 in other docs are stale. Grouped: Memory (8), Conversation (6), Knowledge Base (4), Datapack (5), Database (3).
-
-## Cloud Free-Tier gating at a glance
-
-Some tools return `{"error": "not_available", "detail": "..."}` on cloud Free Tier. This is a server-side tier block — don't retry.
-
-- **Gated on Free Tier**: `db_summarize_database`, `db_run_read_only_query`, `db_run_write_query`, `knowledgebase_trigger_index_creation`, `knowledgebase_add_source_to_index`, `knowledgebase_check_index_status`
-- **Works on Free Tier**: all memory tools, all conversation tools, `knowledgebase_search`, all datapack tools, `flush_pending_memory_candidates`
+**22 tools on Cloud Meko** (verified against `https://mcp.mekodata.ai/mcp`). Grouped: Memory (8), Conversation (6), Knowledge Base (1), Datapack (5), Artifacts (2), Observability (1).
 
 ## Quick health check before using tools
 
 Before starting a session, verify that the Meko MCP tools are working:
 
 1. `memory_search(scope="read", query="test", agent_id="<your-session-agent-id>", conversation_id="<session-conversation-id>")` — Confirms memory subsystem is up. Use the `agent_id` and `conversation_id` from the SessionStart `additionalContext`. May fail with "connection already closed" — see `tools-troubleshooting.md`.
-2. `datapack_list(scope="read")` — Confirms Meko API connectivity
-3. `db_summarize_database(scope="read")` — *Optional, paid-tier only.* On free-tier datapacks this returns `{"error": "not_available"}`. The old "use this for `agent_id` discovery" protocol is retired — use the session-injected `agent_id` for project-scoped calls, or `meko_agent` for the common bucket.
+2. `datapack_list(scope="read")` — Confirms Meko API connectivity. Returns the datapacks your token has access to.
 
 ## Decision tree: which tool do I need?
 
 ```
 User wants to...
-├── Query or explore the database?
-│   ├── See what tables exist? ---------> db_summarize_database (read)
-│   ├── Run a SELECT / read query? -----> db_run_read_only_query (read)
-│   └── INSERT / UPDATE / DELETE? -------> db_run_write_query (write)
-├── Query or build a knowledge base (RAG)?
-│   ├── Search chunks in an existing KB? -> knowledgebase_search (read) — WORKS on cloud today
-│   ├── Create a new index from sources? -> knowledgebase_trigger_index_creation (write) — Free-Tier gated, self-hosted only
-│   ├── Add source to existing index? ---> knowledgebase_add_source_to_index (write) — Free-Tier gated
-│   └── Check build progress? -----------> knowledgebase_check_index_status (read) — Free-Tier gated
+├── Search a knowledge base? ---------------> knowledgebase_search (read)
+├── Add documents to a knowledge base? -----> point user at Meko UI: Datapack → Actions → Add Knowledge
+│                                              (no MCP tool — Cloud uses UI ingestion only)
 ├── Store or recall information?
 │   ├── Store a fact/preference/entity? -----------> memory_add (write)
 │   ├── Store a full conversation (multi-turn)? ---> conversation_create + conversation_add_message (write)
 │   ├── Search past knowledge? --------------------> memory_search (read)
 │   └── Retrieve a past conversation? -------------> conversation_get (read)
+├── Persist or retrieve a file?
+│   ├── Upload a generated file (report, CSV, PDF)? -> artifact_put (write)
+│   └── Retrieve a previously uploaded file? -------> artifact_get (read)
 └── Manage datapacks?
-    └── CRUD datapack? -> datapack_create/list/describe/update/delete
+    └── CRUD datapack? --------------------> datapack_create/list/describe/update/delete
 ```
 
 Agent / knowledge-base lifecycle is managed **outside** the MCP surface — typically in the Meko control-plane UI — and is not exposed as tools here.
 
-## Database Tools (3)
-
-| Tool | Scope | Purpose |
-|------|-------|---------|
-| `db_summarize_database(scope, schema="public", datapack_id=None)` | read | List tables with column schemas and row counts |
-| `db_run_read_only_query(scope, query, datapack_id=None)` | read | Run SELECT, returns JSON. Uses `BEGIN READ ONLY` + `ROLLBACK` |
-| `db_run_write_query(scope, query, datapack_id=None)` | write | Execute INSERT/UPDATE/DELETE/CREATE TABLE. Guardrail-validated. Auto-committed |
-
-## RAG / Knowledge Base Tools (4)
+## Knowledge Base Tools (1)
 
 | Tool | Scope | Purpose |
 |------|-------|---------|
-| `knowledgebase_search(scope, query, agent_id, conversation_id, datapack_id, limit=10)` | read | Semantic search across KB chunks. `datapack_id` is REQUIRED (no default). Works on cloud today. |
-| `knowledgebase_trigger_index_creation(scope, conversation_id, source_uris, index_name, ai_provider="OPENAI", embedding_model="text-embedding-3-large", embedding_dimensions=1536, chunk_size=1024, chunk_overlap=256, datapack_id=None)` | write | Register sources + init vector index + trigger build. **S3-only worker + no user creds; Free-Tier gated on cloud.** See `tools-rag-workflow.md`. |
-| `knowledgebase_add_source_to_index(scope, conversation_id, index_name, source_uri, chunk_size=1024, chunk_overlap=256, datapack_id=None)` | write | Add a new source (URI, not id) to an existing index. Free-Tier gated on cloud. |
-| `knowledgebase_check_index_status(scope, conversation_id, index_name, datapack_id=None)` | read | Check build progress via `dist_rag.vector_index_pipeline_details`. Free-Tier gated on cloud. |
+| `knowledgebase_search(scope, query, agent_id, conversation_id, datapack_id, limit=10)` | read | Semantic search across KB chunks. `datapack_id` is REQUIRED (no default). |
 
 ## Memory Tools (8)
 
@@ -69,7 +47,7 @@ Agent / knowledge-base lifecycle is managed **outside** the MCP surface — typi
 | `memory_update(scope, memory_id, text, agent_id, conversation_id, datapack_id=None)` | write | Overwrite memory text |
 | `memory_delete_by_id(scope, memory_id, agent_id, conversation_id, datapack_id=None)` | write | Delete a single memory |
 | `memory_delete_all(scope, agent_id, conversation_id, user_id=None, app_id=None, run_id=None, datapack_id=None)` | admin | Delete all memories for agent (destructive) |
-| `flush_pending_memory_candidates(scope, agent_id)` | read | Desktop-skill helper: returns an instruction payload telling the agent to scan recent user turns and `memory_add` unsaved facts. No server-side DB write. |
+| `flush_pending_memory_candidates(scope, agent_id)` | read | **Deprecated.** Superseded by automatic extraction from posted turns — post substantive turns with `conversation_add_message` and the server extracts memories from them. Now returns a `deprecated` payload pointing at `conversation_add_message`; kept one release for backward compatibility. |
 
 ## Conversation Tools (6)
 
@@ -88,9 +66,24 @@ Agent / knowledge-base lifecycle is managed **outside** the MCP surface — typi
 |------|-------|---------|
 | `datapack_create(scope, name)` | write | Create new datapack |
 | `datapack_list(scope)` | read | List all datapacks |
-| `datapack_describe(scope, name, include_status=False)` | read | Describe datapack |
-| `datapack_update(scope, name, connection_string)` | write | Update connection string |
-| `datapack_delete(scope, name)` | admin | Delete datapack (irreversible) |
+| `datapack_describe(scope, datapack_id, include_status=False)` | read | Describe datapack by UUID |
+| `datapack_update(scope, datapack_id, connection_string)` | write | Update connection string |
+| `datapack_delete(scope, datapack_id)` | admin | Delete datapack by UUID (irreversible) |
+
+## Artifact Tools (2)
+
+Content-addressed blob store scoped to a datapack. Files < 1 MB go inline in the DB; files ≥ 1 MB go to S3. Identity is SHA-256 — uploading the same bytes twice returns the same `content_hash`. Free-tier artifacts expire after 30 days of inactivity; pro-tier artifacts have no TTL.
+
+| Tool | Scope | Purpose |
+|------|-------|---------|
+| `artifact_put(scope, filename, content_base64, content_type, conversation_id, datapack_id=None, agent_id=None)` | write | Upload a file to the datapack. Returns `{artifact_id, content_hash, filename, size_bytes, stored_in}`. Max 5 MiB (configurable via `MEKO_MAX_ARTIFACT_UPLOAD_BYTES`). |
+| `artifact_get(scope, content_hash, conversation_id, datapack_id=None, agent_id=None)` | read | Retrieve a file by SHA-256 hash. Small files return `content_base64` inline; large files (S3) are written to `~/.meko/artifacts/<hash>/<filename>` and `local_path` is returned. |
+
+## Observability Tools (1)
+
+| Tool | Scope | Purpose |
+|------|-------|---------|
+| `track_token_usage(scope, conversation_id, name, input_tokens=0, output_tokens=0, total_tokens=None, model=None, message_id=None, datapack_id=None)` | write | Record an LLM-cost GENERATION observation on the conversation's trace. Primarily called by first-party Meko services (e.g. inference_gateway) that know their LLM's exact token counts. Most end-agents (Cursor, Claude Desktop) don't have those counts at the MCP call layer, so this tool is rarely useful for third-party agents. |
 
 ## Platform capabilities NOT exposed via MCP
 
@@ -98,15 +91,15 @@ Some things the Meko platform can do are not wired into the MCP tool surface tod
 
 | Capability | Where it lives | How to reach it |
 |---|---|---|
-| Create / list / delete **agents** within a datapack | `yugabyte/meko` API server | REST: `POST/GET/DELETE /datapacks/:name/agents` (`POST/GET/DELETE /agents/:agent` for targeted deletes), or the Meko control-plane UI |
-| Add / list / delete **knowledge-base sources** on a datapack | `yugabyte/meko` API server | REST: `POST/GET/DELETE /datapacks/:name/knowledge-bases`, plus `upload-url`, `upload-complete`, `create`, `status` subroutes. Also available in the Meko UI. |
-| Langfuse project-key generation | `yugabyte/meko` API server | REST: `POST /datapacks/:name/langfuse/project-keys` |
+| Create / list / delete **agents** within a datapack | `yugabyte/meko` API server | REST: `POST/GET/DELETE /datapacks/:datapack_id/agents` (`POST/GET/DELETE /agents/:agent` for targeted deletes), or the Meko control-plane UI |
+| Add / list / delete **knowledge-base sources** on a datapack | `yugabyte/meko` API server | REST: `POST/GET/DELETE /datapacks/:datapack_id/knowledge-bases`, plus `upload-url`, `upload-complete`, `create`, `status` subroutes. Also available in the Meko UI. |
+| Langfuse project-key generation | `yugabyte/meko` API server | REST: `POST /datapacks/:datapack_id/langfuse/project-keys` |
 | Account / billing / tier management | Meko UI only | Not available via MCP or public REST |
 
 The MCP-exposed `datapack_create` / `datapack_list` / `datapack_describe` / `datapack_update` / `datapack_delete` tools above are a deliberate subset — the common CRUD that an agent reasonably needs mid-conversation. Anything involving agent or KB lifecycle is control-plane territory.
 
-For knowledge-base content on cloud today, the canonical path is **UI upload**: Datapack → Actions → **Add Knowledge** (PDF/TXT/MD/JSON/MP4, 5MB each, 10/batch). `knowledgebase_search` queries the resulting index from MCP. The MCP ingestion tools (`knowledgebase_trigger_index_creation`, `knowledgebase_add_source_to_index`, `knowledgebase_check_index_status`) exist but are Free-Tier gated and rely on an S3-only worker with no user-supplied credentials — see `tools-rag-workflow.md` for the full picture. Tracked upstream as [#89](https://github.com/yugabyte/meko-mcp-server/issues/89) / MEKO-96.
+For knowledge-base content on Cloud, the canonical path is **UI upload**: Datapack → Actions → **Add Knowledge** (PDF/TXT/MD/JSON/MP4, 5MB each, 10/batch). `knowledgebase_search` queries the resulting index from MCP.
 
 ## Common Parameter Patterns
 
-Every tool accepts `scope` as the first parameter. All DB, RAG, and memory tools accept optional `datapack_id` to target a specific datapack's database. Memory and conversation tools require `agent_id` for namespace isolation (see `tools-agent-id-conventions.md`).
+Every tool accepts `scope` as the first parameter. Memory and KB tools accept optional `datapack_id` to target a specific datapack. Memory and conversation tools require `agent_id` for namespace isolation (see `tools-agent-id-conventions.md`).

package/assets/skills/meko-mcp-tools/references/tools-rag-workflow.md

@@ -1,19 +1,16 @@
 # Knowledge Base / RAG workflow
 
-As of 2026-05-07, **knowledge-base ingestion on cloud Meko is a UI-only activity**. The MCP ingestion tools exist but are gated off on cloud and rely on an S3-only worker that has no mechanism to read user-supplied buckets. `knowledgebase_search` is the only KB tool agents can rely on today.
-
-This page tells you which tool to reach for, what's usable where, and where the current gaps are tracked.
+`knowledgebase_search` is the only KB tool exposed via MCP. Index
+creation and ingestion happen out of band — through the **Meko UI**
+(`cloud.mekodata.ai`).
 
 ## Decision table
 
 | Situation | Use this | Why |
 |---|---|---|
-| Search an existing KB | `knowledgebase_search` | The one KB tool that works on cloud Free Tier and prod today |
-| Add documents to a KB on cloud | **Meko UI** — Datapack → Actions menu → **Add Knowledge** | File-upload dialog (PDF/TXT/MD/JSON/MP4, 5MB each, 10/batch). The MCP ingestion path is not usable on cloud |
-| Create a new vector index (self-hosted / paid) | `knowledgebase_trigger_index_creation` | Only works when the ingestion worker has IAM access to the S3 bucket you pass |
-| Add a source to an existing index (self-hosted / paid) | `knowledgebase_add_source_to_index` | Same caveat as above |
-| Poll a build (self-hosted / paid) | `knowledgebase_check_index_status` | Gated on cloud Free Tier |
-| Anything that needs KB lifecycle management (list, delete, rename) | **UI** | No MCP tools for KB lifecycle |
+| Search an existing KB | `knowledgebase_search` | The one KB tool exposed via MCP |
+| Add documents to a KB | **Meko UI** — Datapack → Actions → **Add Knowledge** | File-upload dialog (PDF/TXT/MD/JSON/MP4, 5 MB each, 10/batch). No MCP equivalent |
+| Anything else (list / delete / rename / re-index) | **UI** | No MCP tools for KB lifecycle |
 
 ## knowledgebase_search — the one you'll actually call
 
@@ -27,60 +24,16 @@ knowledgebase_search(
     limit=10)
 ```
 
-Required: `scope`, `query`, `agent_id`, `conversation_id`, `datapack_id`. Unlike the memory tools, `datapack_id` has no default here — you must pass it explicitly. `agent_id` is **ignored for filtering** on this tool (KB results are team-shared on the datapack), but you still pass it — your session's value is fine.
-
-Response shape (verified 2026-05-07 against prod):
-```
-{"results": [], "count": 0}
-```
-
-On a populated KB each result carries chunk content and similarity scores. On an empty or nonexistent KB you get an empty array and `count: 0` — not an error.
-
-## MCP ingestion tools — what actually happens when you call them
-
-This applies to `knowledgebase_trigger_index_creation` and `knowledgebase_add_source_to_index`. Understanding the two-layer architecture is the only way to predict whether a call will succeed.
-
-**MCP layer (`src/tools.py`):** takes `source_uris`, splits on `,`, passes each string to `dist_rag.create_source(<uri>)` with **zero validation**. No scheme check, no reachability probe. Returns `"build_triggered"` immediately.
-
-**Worker layer (`yugabyte-db/python/ai/rag_agent/rag_pipeline/aws_source_processor.py`):** only handles `s3://` URIs. Any other scheme raises `ValueError("Invalid source URI")` inside the worker — **async, never surfaced to the MCP caller**. The S3 crawler is instantiated with no credentials; it relies on boto3's default chain (env vars, IAM role, `~/.aws/credentials` on the worker host). So the worker can only read buckets its own AWS identity has access to.
-
-**Implication:** pointing the MCP tool at a user-owned S3 bucket from cloud will return `"build_triggered"` and silently stall at INIT forever. There is no way for the user to supply AWS credentials through the MCP tool.
-
-## Free-Tier cloud gating (verified 2026-05-07 against `https://mcp.mekodata.ai/mcp`)
-
-| Tool | Verbatim response |
-|---|---|
-| `knowledgebase_trigger_index_creation` | `{"error": "not_available", "detail": "Vector index creation is not available on the free tier."}` |
-| `knowledgebase_add_source_to_index` | Same as above |
-| `knowledgebase_check_index_status` | `{"error": "not_available", "detail": "Index status check is not available on the free tier."}` |
-| `knowledgebase_search` | Works: `{"results": [], "count": 0}` |
-
-`{"error": "not_available"}` is a server-side tier block. Don't retry.
-
-## UI ingestion (cloud Meko) — what the user sees
-
-From `cloud.mekodata.ai`:
-
-1. Open a datapack (`/datapacks/<name>`).
-2. Click **Actions** → **Add Knowledge**.
-3. Drag-and-drop or browse for files. Supported: PDF, TXT, MD, JSON, MP4. Per-file limit 5 MB. Up to 10 files per batch.
-4. The UI handles upload, storage, and index build. The user does not pick a bucket or provide credentials.
-5. Search results from `knowledgebase_search` become available once indexing completes.
-
-If a user asks you "how do I add a document to my knowledge base?", point them at this flow. Do not suggest `knowledgebase_trigger_index_creation` with an S3 URI — on cloud that path does not work.
+Required: `scope`, `query`, `agent_id`, `conversation_id`, `datapack_id`.
+Unlike the memory tools, `datapack_id` has no default here — you must
+pass it explicitly. `agent_id` is **ignored for filtering** on this
+tool (KB results are team-shared on the datapack), but you still pass
+it — your session's value is fine.
 
-## Tracked gaps
-
-- **Upstream GitHub**: [yugabyte/meko-mcp-server#89](https://github.com/yugabyte/meko-mcp-server/issues/89) — disable or gate KB ingestion tools on cloud until the S3 path works end-to-end; return a clearer error than "not_available"; validate schemes at MCP-call time.
-- **Upstream Jira**: MEKO-96 (same issue, cross-linked).
-
-When either lands, the free-tier-gate responses above will change and this page should be revisited.
-
-## Response-shape reference (for agents that need to parse)
-
-### knowledgebase_search
+## Response shape
 
 Populated KB:
+
 ```
 {
   "results": [
@@ -97,38 +50,21 @@ Populated KB:
 }
 ```
 
-Empty or nonexistent KB: `{"results": [], "count": 0}` (no error).
-
-### knowledgebase_trigger_index_creation (when not gated)
-
-Success shape:
-```
-{
-  "source_ids": ["<uuid>", ...],
-  "index_id": "<uuid>",
-  "index_name": "<name>",
-  "status": "build_triggered",
-  "message": "N source(s) registered, index '...' initialised, and build triggered."
-}
-```
-
-Do NOT retry this on failure. Each call creates a new index.
-
-### knowledgebase_add_source_to_index (when not gated)
-
-The historical `r_index_name` vs `r_index_id` parameter-mismatch bug is fixed on main (`src/tools.py` resolves `index_name → index_id` via `SELECT id FROM dist_rag.vector_indexes WHERE index_name = %s` before calling the dist_rag function). If `index_name` doesn't exist you get `{"error": "index_not_found", "detail": "No vector index found with name '...'"}`.
-
-Param is `source_uri` (URI string like `s3://bucket/path/`), **not** `source_id` as older docs may claim.
+Empty or nonexistent KB: `{"results": [], "count": 0}` (no error,
+just an empty array).
 
-### knowledgebase_check_index_status (when not gated)
+## UI ingestion — what the user sees
 
-Returns `pipeline_details` (per-document status) and `pipeline_stats` (aggregated). Check `completion_rate_percent` in `pipeline_stats` and `document_status` in `pipeline_details`.
-
-Stuck at INIT for >5 minutes under self-hosted usually means the worker couldn't reach the bucket — check AWS credentials on the worker host, not the MCP server.
-
-## Prerequisites (self-hosted)
+From `cloud.mekodata.ai`:
 
-- `dist_rag` PostgreSQL extension enabled on the target YugabyteDB database
-- Ingestion workers running (`yugabyte-db/python/ai/rag_agent/`)
-- AWS credentials on the worker host for any S3 bucket you intend to ingest from
-- `datapack_id` passed on every call when targeting a non-default datapack
+1. Open a datapack (`/datapacks/<name>`).
+2. Click **Actions** → **Add Knowledge**.
+3. Drag-and-drop or browse for files. Supported: PDF, TXT, MD, JSON,
+   MP4. Per-file limit 5 MB. Up to 10 files per batch.
+4. The UI handles upload, storage, and index build. The user does not
+   pick a bucket or provide credentials.
+5. Search results from `knowledgebase_search` become available once
+   indexing completes.
+
+If a user asks you "how do I add a document to my knowledge base?",
+point them at this flow.

package/assets/skills/meko-mcp-tools/references/tools-scope-permissions.md

@@ -1,6 +1,6 @@
 # Scope Permission Hierarchy and Per-Tool Requirements
 
-**WRONG:** `db_run_write_query(scope="read", ...)` → PermissionError: requires 'write' or higher.
+**WRONG:** `memory_add(scope="read", ...)` → PermissionError: requires 'write' or higher.
 **WRONG:** `memory_delete_all(scope="write", ...)` → PermissionError: requires 'admin'.
 
 ## Scope Hierarchy
@@ -17,13 +17,11 @@ Higher scopes include lower scopes. An unrecognized scope string always fails.
 
 ## Per-Tool Requirements
 
-### read scope (11 tools)
+### read scope (9 tools)
 
 | Tool | Group |
 |------|-------|
-| `db_summarize_database` | Database |
-| `db_run_read_only_query` | Database |
-| `knowledgebase_check_index_status` | RAG |
+| `knowledgebase_search` | RAG |
 | `memory_search` | Memory |
 | `memory_get_by_id` | Memory |
 | `memory_get_all` | Memory |
@@ -33,13 +31,10 @@ Higher scopes include lower scopes. An unrecognized scope string always fails.
 | `datapack_list` | Datapack |
 | `datapack_describe` | Datapack |
 
-### write scope (11 tools)
+### write scope (9 tools)
 
 | Tool | Group |
 |------|-------|
-| `db_run_write_query` | Database |
-| `knowledgebase_trigger_index_creation` | RAG |
-| `knowledgebase_add_source_to_index` | RAG |
 | `memory_add` | Memory |
 | `memory_update` | Memory |
 | `memory_delete_by_id` | Memory |
@@ -48,6 +43,7 @@ Higher scopes include lower scopes. An unrecognized scope string always fails.
 | `conversation_update` | Conversation |
 | `datapack_create` | Datapack |
 | `datapack_update` | Datapack |
+| `track_token_usage` | Observability |
 
 ### admin scope (3 tools — destructive, irreversible)
 

package/assets/skills/meko-mcp-tools/references/tools-troubleshooting.md

@@ -13,7 +13,7 @@ These patterns are extracted from real agent sessions. Follow them to avoid wast
 
 ## Connection errors: "connection already closed"
 
-**Affects:** Memory tools (`memory_add`, `memory_search`, `memory_get_all`) most frequently. DB tools less often.
+**Affects:** Memory tools (`memory_add`, `memory_search`, `memory_get_all`) most frequently.
 
 **Why it happens:** The Python memory subsystem uses a connection cache that doesn't recover from dropped connections (unlike the Go API server which has retry logic with 5 retries and 3-second delays).
 
@@ -21,73 +21,11 @@ These patterns are extracted from real agent sessions. Follow them to avoid wast
 
 1. Retry the same call **once**.
 2. If it fails again, the memory subsystem is unhealthy for this session — stop trying memory calls and tell the user. Do not waste tokens re-sending the same payload.
-3. Direct-SQL fallback **does not apply** on cloud Free Tier (`db_run_read_only_query` returns `{"error": "not_available", "detail": "Free Tier: DB Tools access is not enabled. coming soon."}`). On self-hosted / paid deployments where DB tools are available, inspect memory rows via the multi-tenant schema — tables are namespaced by datapack, not by agent_id. The old `{agent_id}_mem0_collection` per-agent-table layout is gone.
 
 **Anti-pattern from real sessions:** Agent called `memory_add` with 500+ tokens of text, got "connection already closed", retried the identical call 3 more times (each 500+ tokens). Wasted ~2000 tokens on guaranteed failures.
 
 ---
 
-## RAG pipeline stuck at INIT
-
-**Affects:** `knowledgebase_trigger_index_creation` — the build triggers but never completes.
-
-**Symptoms:**
-- `knowledgebase_check_index_status` returns empty `pipeline_details` and `pipeline_stats`
-- Documents remain at `INIT` status indefinitely
-- Work queue tasks are `IN_PROGRESS` with `lease_expires_at` in the past
-
-**Diagnosis:** Query the work queue directly:
-```
-db_run_read_only_query(scope="read",
-    query="SELECT task_type, status, lease_expires_at FROM dist_rag.work_queue WHERE index_name = 'your_index' ORDER BY created_at DESC LIMIT 10")
-```
-
-Look for tasks stuck `IN_PROGRESS` with expired leases — these indicate crashed or hung workers.
-
-**What to do:**
-
-1. Poll status **at most 3 times** with 1-2 minute intervals
-2. If no progress after 3 checks, **stop polling** — the pipeline is stuck
-3. There is **no way to reset or retry stuck tasks via MCP tools**
-4. Creating a new index with a different name (e.g., `_v2`) is a workaround, but if the workers themselves are down, this will also get stuck
-5. Recommend the user check worker logs or restart the pipeline service
-
-**Anti-pattern from real sessions:** Agent created indexes `v1`, `v2`, `v3` — all stuck with the same symptoms. Even making the S3 bucket public didn't help. The issue was worker infrastructure, not permissions.
-
----
-
-## db_run_write_query guardrail error
-
-**Error:** `'dict' object has no attribute 'guardrail_config'`
-
-**Affects:** `db_run_write_query` in some deployments.
-
-**What to do:**
-
-1. Try the call once. If it fails with this specific error, write operations are unavailable in this deployment.
-2. For reads, always use `db_run_read_only_query` (never `db_run_write_query` for SELECT).
-3. Report the issue — it's a server-side bug, not a parameter problem.
-
----
-
-## knowledgebase_add_source_to_index failure
-
-**Error shape:** `{"error": "not_available", "detail": "Vector index creation is not available on the free tier."}`
-
-You're on cloud Free Tier; the ingestion tools are gated off. There is no retry that will succeed. Point the user at the Meko UI's **Add Knowledge** file-upload flow (Datapack → Actions → Add Knowledge) instead.
-
-**Error shape:** `{"error": "index_not_found", "detail": "No vector index found with name '...'"}`
-
-The `index_name` doesn't exist in this datapack's `dist_rag.vector_indexes` table. Either you're targeting the wrong datapack (check `datapack_id`), or the index hasn't been created yet — call `knowledgebase_trigger_index_creation` first.
-
-**Error shape:** tool returns `"build_triggered"` but `knowledgebase_check_index_status` shows documents stuck at `INIT` for >5 minutes.
-
-Most common cause on self-hosted deployments: the worker can't reach the S3 bucket. `S3BucketCrawler()` uses boto3's default credential chain — check `AWS_ACCESS_KEY_ID` / `AWS_SECRET_ACCESS_KEY` / IAM role / `~/.aws/credentials` on the worker host, not on the MCP server. Second cause: the URI isn't `s3://`-prefixed (`aws_source_processor.py` rejects other schemes with `ValueError("Invalid source URI")` async).
-
-**Historical note:** the old `r_index_name` vs `r_index_id` parameter-mismatch bug is fixed on main — the MCP tool now resolves `index_name → index_id` internally via a `SELECT id FROM dist_rag.vector_indexes WHERE index_name = %s` step. Older docs referencing this bug are stale.
-
----
-
 ## Scope parameter errors
 
 **Error:** `Insufficient scope: 'all'. This tool requires 'read' or higher.`
@@ -124,21 +62,6 @@ Pre-existing data may be tagged `"agent"`, `"claude_code"`, `"cursor:<slug>"`, o
 
 ---
 
-## Permission denied on data tables
-
-**Error:** `permission denied for table customer_complaints`
-
-**Why:** The MCP database user may not have read access to all tables, particularly data tables created by the provisioning system within a datapack.
-
-**What to do:**
-
-1. This is a server-side configuration issue — not fixable via MCP tools.
-2. Don't retry. Don't try different query formulations.
-3. Use `db_summarize_database` to see which tables you CAN access.
-4. Report the permission gap to the Meko admin.
-
----
-
 ## Safe-to-retry vs not
 
 | Tool | Safe to retry? | Why |
@@ -147,9 +70,6 @@ Pre-existing data may be tagged `"agent"`, `"claude_code"`, `"cursor:<slug>"`, o
 | `memory_add` | Yes (once) | Mem0 has dedup logic |
 | `memory_update` | Yes (once) | Overwrites same ID |
 | `memory_delete_by_id` | Yes | Deleting already-deleted is a no-op |
-| `db_run_write_query` (INSERT) | **No** | May double-insert rows |
-| `db_run_write_query` (CREATE TABLE) | **No** | "Table already exists" error |
-| `knowledgebase_trigger_index_creation` | **No** | Creates duplicate indexes |
 | `conversation_create` | **No** | Creates duplicate conversations |
 | `conversation_add_message` with `seed` | Yes | Seed-based dedup prevents duplicates |
 | `conversation_add_message` without `seed` | **No** | Creates duplicate messages |