@cabane/companion 0.6.141 → 0.6.142

package/dist/cli.js

@@ -2564,8 +2564,7 @@ var init_addendum = __esm({
     CLAUDE_CODE_ADDENDUM = [
       "On this harness the Cabane tools register under MCP prefixes. The workspace tools are",
       "`mcp__cabane__query`, `mcp__cabane__mutate` and `mcp__cabane__describe`; the ancillary",
-      "tools are `mcp__cabane__list_workspaces`,",
-      "`mcp__cabane__read_binary`, `mcp__cabane__upload`, `mcp__cabane__begin_upload`,",
+      "tools are `mcp__cabane__read_binary`, `mcp__cabane__upload`, `mcp__cabane__begin_upload`,",
       "`mcp__cabane__finalize_upload`, and `mcp__cabane__mint_render_token`.",
       turnControlPromptGuidance("mcp__cabane_companion__"),
       "Where this prompt names a tool by its bare verb, call",
@@ -3890,7 +3889,7 @@ var init_addendum2 = __esm({
       "Every tool here goes by its plain name: the workspace tools are `query`, `mutate` and",
       "`describe`.",
       turnControlPromptGuidance(""),
-      "The ancillary tools are `list_workspaces`, `read_binary`, `upload`, `begin_upload`,",
+      "The ancillary tools are `read_binary`, `upload`, `begin_upload`,",
       "`finalize_upload`, `mint_render_token`; and the host tools are plain verbs too (`bash`,",
       "`read`, `edit`). Mind the collision: a bare `read` or `edit` is the HOST tool, acting on the",
       "local machine \u2014 a workspace read is `query` with the operation name `files.read`. The",
@@ -5075,8 +5074,8 @@ var init_addendum3 = __esm({
       // in sat two lines under the instruction to invoke the exact qualified names,
       // so the sentence contradicted itself. The bare `query` / `mutate` below stay:
       // that sentence is about operation names, after the qualified forms are given.
-      "The ancillary tools are `mcp__cabane__list_workspaces`, `mcp__cabane__read_binary`,",
-      "`mcp__cabane__upload`, `mcp__cabane__begin_upload`, `mcp__cabane__finalize_upload` and",
+      "The ancillary tools are `mcp__cabane__read_binary`, `mcp__cabane__upload`,",
+      "`mcp__cabane__begin_upload`, `mcp__cabane__finalize_upload` and",
       "`mcp__cabane__mint_render_token` \u2014 all possibly deferred too.",
       "There is no Cabane `read`/`write`/`search` tool \u2014 those are",
       "operation NAMES you pass to `query` / `mutate`. One more harness fact: you can interleave",

package/dist/runtime.js

@@ -3990,8 +3990,7 @@ function turnControlPromptGuidance(prefix) {
 var CLAUDE_CODE_ADDENDUM = [
   "On this harness the Cabane tools register under MCP prefixes. The workspace tools are",
   "`mcp__cabane__query`, `mcp__cabane__mutate` and `mcp__cabane__describe`; the ancillary",
-  "tools are `mcp__cabane__list_workspaces`,",
-  "`mcp__cabane__read_binary`, `mcp__cabane__upload`, `mcp__cabane__begin_upload`,",
+  "tools are `mcp__cabane__read_binary`, `mcp__cabane__upload`, `mcp__cabane__begin_upload`,",
   "`mcp__cabane__finalize_upload`, and `mcp__cabane__mint_render_token`.",
   turnControlPromptGuidance("mcp__cabane_companion__"),
   "Where this prompt names a tool by its bare verb, call",
@@ -5228,7 +5227,7 @@ var OPENCODE_ADDENDUM = [
   "Every tool here goes by its plain name: the workspace tools are `query`, `mutate` and",
   "`describe`.",
   turnControlPromptGuidance(""),
-  "The ancillary tools are `list_workspaces`, `read_binary`, `upload`, `begin_upload`,",
+  "The ancillary tools are `read_binary`, `upload`, `begin_upload`,",
   "`finalize_upload`, `mint_render_token`; and the host tools are plain verbs too (`bash`,",
   "`read`, `edit`). Mind the collision: a bare `read` or `edit` is the HOST tool, acting on the",
   "local machine \u2014 a workspace read is `query` with the operation name `files.read`. The",
@@ -6333,8 +6332,8 @@ var CODEX_ADDENDUM = [
   // in sat two lines under the instruction to invoke the exact qualified names,
   // so the sentence contradicted itself. The bare `query` / `mutate` below stay:
   // that sentence is about operation names, after the qualified forms are given.
-  "The ancillary tools are `mcp__cabane__list_workspaces`, `mcp__cabane__read_binary`,",
-  "`mcp__cabane__upload`, `mcp__cabane__begin_upload`, `mcp__cabane__finalize_upload` and",
+  "The ancillary tools are `mcp__cabane__read_binary`, `mcp__cabane__upload`,",
+  "`mcp__cabane__begin_upload`, `mcp__cabane__finalize_upload` and",
   "`mcp__cabane__mint_render_token` \u2014 all possibly deferred too.",
   "There is no Cabane `read`/`write`/`search` tool \u2014 those are",
   "operation NAMES you pass to `query` / `mutate`. One more harness fact: you can interleave",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cabane/companion",
-  "version": "0.6.141",
+  "version": "0.6.142",
   "type": "module",
   "description": "The Cabane Companion (headless): connect a coding agent on your machine to your Cabane workspace as a responder — drive work against your own codebase, files, and MCP servers without putting any of it in Cabane.",
   "license": "UNLICENSED",