@vincemakes/kiso-provider-openai-responses 0.47.1 → 0.47.3

package/dist/index.js

@@ -140,10 +140,17 @@ function buildBody(options, target, scopeProviderId) {
     };
 }
 function toResponsesTool(tool) {
-    // No `strict`: the flag changes the PROVIDER's validation semantics,
-    // and kiso's schemas are already closed worlds validated by the kernel
-    // (PH-1a.1). Sending it would claim a second, disagreeing validator.
-    return { type: "function", name: tool.name, description: tool.description, parameters: tool.inputSchema };
+    // `strict: false`, said explicitly. kiso's schemas are closed worlds the
+    // kernel validates (PH-1a.1), so no provider-side validator is wanted —
+    // but on the Responses API an ABSENT flag is not "off": the ChatGPT
+    // backend then forces every declared property into the call, and the
+    // model fills the optional ones with placeholders (`readyWhen: ""`
+    // detached a one-shot command; an empty second edit form refused every
+    // edit). One request per arm on gpt-6.1-sol, 2026-10-08: absent → all
+    // four optional shell fields sent; false → only `command`. The vendor's
+    // own client sends `strict: false` too. Reverses this adapter's earlier
+    // "no `strict`" note, which read absent as off.
+    return { type: "function", name: tool.name, description: tool.description, parameters: tool.inputSchema, strict: false };
 }
 function toInputContent(content) {
     if (typeof content === "string")

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vincemakes/kiso-provider-openai-responses",
-	"version": "0.47.1",
+	"version": "0.47.3",
 	"description": "kiso OpenAI Responses adapter \u2014 the first-party Responses API and the ChatGPT subscription backend, one adapter, plain fetch + SSE.",
 	"type": "module",
 	"license": "MIT",
@@ -21,7 +21,7 @@
 		"test": "vitest run"
 	},
 	"dependencies": {
-		"@vincemakes/kiso-core": "0.47.1"
+		"@vincemakes/kiso-core": "0.47.3"
 	},
 	"devDependencies": {
 		"@types/node": "^26.1.2",