carrick 0.3.85 → 0.3.86

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "carrick",
-  "version": "0.3.85",
+  "version": "0.3.86",
   "description": "The API contract index for a TypeScript workspace: what the other services do with the routes and calls in the file you are editing, in your editor and in your agent's context",
   "keywords": [
     "typescript",
@@ -58,11 +58,11 @@
     "zod": "^3.23.0"
   },
   "optionalDependencies": {
-    "@carrick-tools/cli-darwin-arm64": "0.3.85",
-    "@carrick-tools/cli-darwin-x64": "0.3.85",
-    "@carrick-tools/cli-linux-arm64": "0.3.85",
-    "@carrick-tools/cli-linux-x64": "0.3.85",
-    "@carrick-tools/cli-win32-x64": "0.3.85"
+    "@carrick-tools/cli-darwin-arm64": "0.3.86",
+    "@carrick-tools/cli-darwin-x64": "0.3.86",
+    "@carrick-tools/cli-linux-arm64": "0.3.86",
+    "@carrick-tools/cli-linux-x64": "0.3.86",
+    "@carrick-tools/cli-win32-x64": "0.3.86"
   },
   "devDependencies": {
     "@types/node": "^24.13.3",

package/sidecar/dist/src/type-inferrer.d.ts

@@ -708,7 +708,16 @@ export declare class TypeInferrer {
      * True when an object literal argument is response INIT rather than a body:
      * every property it declares is one the standard `ResponseInit` declares
      * (`status`, `statusText`, `headers`), and it states at least one of them as
-     * init really does — a numeric status in the HTTP range, or headers.
+     * init really does — a status in the HTTP range, or headers.
+     *
+     * The status does NOT have to be a literal code. A route that carries its
+     * outcome in a value writes `new Response(body, { status: result.status })`,
+     * where the source fixes no code and `statedStatusCodes` answers
+     * `'variable'` — status-shaped, just not pinned. Requiring a literal there
+     * left the whole init object reading as a body, so an endpoint whose payload
+     * this layer does not publish (a string body) published `{ status: number }`
+     * as its response contract instead: a wrong contract, served, where an
+     * abstention was the honest answer.
      *
      * A payload that merely has a `status` member of its own (`{ status: "ok",
      * service: "ledger" }`) declares members init does not, or states `status` as

package/sidecar/dist/src/type-inferrer.js

@@ -3029,7 +3029,16 @@ export class TypeInferrer {
      * True when an object literal argument is response INIT rather than a body:
      * every property it declares is one the standard `ResponseInit` declares
      * (`status`, `statusText`, `headers`), and it states at least one of them as
-     * init really does — a numeric status in the HTTP range, or headers.
+     * init really does — a status in the HTTP range, or headers.
+     *
+     * The status does NOT have to be a literal code. A route that carries its
+     * outcome in a value writes `new Response(body, { status: result.status })`,
+     * where the source fixes no code and `statedStatusCodes` answers
+     * `'variable'` — status-shaped, just not pinned. Requiring a literal there
+     * left the whole init object reading as a body, so an endpoint whose payload
+     * this layer does not publish (a string body) published `{ status: number }`
+     * as its response contract instead: a wrong contract, served, where an
+     * abstention was the honest answer.
      *
      * A payload that merely has a `status` member of its own (`{ status: "ok",
      * service: "ledger" }`) declares members init does not, or states `status` as
@@ -3058,7 +3067,7 @@ export class TypeInferrer {
                 statesInit = true;
                 continue;
             }
-            if (name === 'status' && Array.isArray(this.statedStatusCodes(value))) {
+            if (name === 'status' && this.statedStatusCodes(value) !== undefined) {
                 statesInit = true;
             }
         }