stitchkit 0.101.2 → 0.101.3

package/CHANGELOG.md

@@ -15,6 +15,17 @@ additive**; the first breaking change landed in 0.10.0. Grep the file for
 
 ## [Unreleased]
 
+## [0.101.3] — 2026-09-29
+
+### Fixed
+
+- **`stitchkit/tools/connections`** — a discovered MCP command whose tool
+  answers with no content parts (a tool without an output contract) prints
+  `null` on the CLI and exits `0`. It printed the whole envelope — the
+  server's `_meta` and an empty `content` — as if that were the answer; a
+  failed call with no parts now fails as `UPSTREAM_TOOL_ERROR` without
+  relaying that envelope either.
+
 ## [0.101.2] — 2026-09-29
 
 ### Added

package/dist/entrypoints/tools/connections.js

@@ -529,6 +529,8 @@ function unwrapMcpResult(result) {
     return result.structuredContent;
   if (!Array.isArray(result.content))
     return result;
+  if (result.content.length === 0)
+    return null;
   const only = result.content.length === 1 ? result.content[0] : undefined;
   if (!isRecord(only) || only.type !== "text" || typeof only.text !== "string")
     return result;

package/dist/tools/connections/mcp-envelope.d.ts

@@ -12,6 +12,10 @@
  * So the CLI unwraps, and only the CLI. The order is the server's own order of
  * preference: `structuredContent` is the answer when the server sent one; a lone
  * text part is the answer when it parses as JSON, and its text when it does not.
+ * No parts at all is no answer, and says so as JSON: `null`. The envelope around
+ * an empty `content` carries only protocol metadata, and `_meta` is never an
+ * answer. Not `undefined`: a discovered tool declares an output, and an absent
+ * value there is a broken handler, not an empty one.
  * Anything else — several parts, an image, audio — is passed through whole,
  * because picking one part out of many would be inventing an answer.
  */

package/dist/tools/connections/mcp-envelope.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"mcp-envelope.d.ts","sourceRoot":"","sources":["../../../src/tools/connections/mcp-envelope.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAEH,OAAO,EAAE,QAAQ,EAAE,MAAM,uBAAuB,CAAC;AAIjD,wBAAgB,eAAe,CAAC,MAAM,EAAE,OAAO,GAAG,OAAO,CAaxD;AAED;;;;;GAKG;AACH,eAAO,MAAM,mBAAmB,wBAAwB,CAAC;AAEzD;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,wBAAgB,cAAc,CAAC,QAAQ,EAAE,MAAM,EAAE,MAAM,EAAE,OAAO,GAAG,QAAQ,CAwB1E"}
+{"version":3,"file":"mcp-envelope.d.ts","sourceRoot":"","sources":["../../../src/tools/connections/mcp-envelope.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;GAoBG;AAEH,OAAO,EAAE,QAAQ,EAAE,MAAM,uBAAuB,CAAC;AAIjD,wBAAgB,eAAe,CAAC,MAAM,EAAE,OAAO,GAAG,OAAO,CAcxD;AAED;;;;;GAKG;AACH,eAAO,MAAM,mBAAmB,wBAAwB,CAAC;AAEzD;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,wBAAgB,cAAc,CAAC,QAAQ,EAAE,MAAM,EAAE,MAAM,EAAE,OAAO,GAAG,QAAQ,CAwB1E"}

package/llms/cli.txt

@@ -912,9 +912,11 @@ kind, because the handler's value is what gets printed, piped and aggregated:
 handed the envelope, `--count-by status` groups the *content parts* and answers
 `no record carries the field "status" — available: text, type`. So the CLI
 transport unwraps, and only it: `structuredContent` when the server sent one, a
-lone text part when it parses as JSON, its text when it does not. Several parts,
-an image or audio pass through whole — picking one of many would be inventing an
-answer.
+lone text part when it parses as JSON, its text when it does not, and `null` when
+there are no parts at all — a tool without an output contract answers that way,
+and the `_meta` beside an empty `content` is protocol metadata, never the answer.
+Several parts, an image or audio pass through whole — picking one of many would
+be inventing an answer.
 
 
 ## Auth parity

package/llms-full.txt

@@ -9067,9 +9067,11 @@ kind, because the handler's value is what gets printed, piped and aggregated:
 handed the envelope, `--count-by status` groups the *content parts* and answers
 `no record carries the field "status" — available: text, type`. So the CLI
 transport unwraps, and only it: `structuredContent` when the server sent one, a
-lone text part when it parses as JSON, its text when it does not. Several parts,
-an image or audio pass through whole — picking one of many would be inventing an
-answer.
+lone text part when it parses as JSON, its text when it does not, and `null` when
+there are no parts at all — a tool without an output contract answers that way,
+and the `_meta` beside an empty `content` is protocol metadata, never the answer.
+Several parts, an image or audio pass through whole — picking one of many would
+be inventing an answer.
 
 
 ## Auth parity

package/llms.txt

@@ -17,7 +17,7 @@ Load the slice for each entrypoint your code imports — `import … from 'stitc
 - **stitchkit/tools/contract**: [llms/tools-contract.txt](llms/tools-contract.txt) 0.2 KB
 - **stitchkit/tools/invoker**: [llms/tools-invoker.txt](llms/tools-invoker.txt) 0.2 KB
 - **stitchkit/tools/connections**: [llms/tools-connections.txt](llms/tools-connections.txt) 3.1 KB
-- **stitchkit/cli**: [llms/cli.txt](llms/cli.txt) 42.7 KB → [llms/cli.2.txt](llms/cli.2.txt) 8.1 KB
+- **stitchkit/cli**: [llms/cli.txt](llms/cli.txt) 42.8 KB → [llms/cli.2.txt](llms/cli.2.txt) 8.1 KB
 - **stitchkit/remote**: [llms/remote.txt](llms/remote.txt) 1.0 KB
 - **stitchkit/contract**: [llms/contract.txt](llms/contract.txt) 31.9 KB
 - **stitchkit/primitives**: [llms/primitives.txt](llms/primitives.txt) 9.3 KB

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "stitchkit",
-  "version": "0.101.2",
+  "version": "0.101.3",
   "description": "Contract-first backend framework — one defineContract() into an HTTP API, MCP tools, AI-agent tools and a typed client. Bun and Node.",
   "keywords": [
     "bun",