@sunerpy/kiro-provider 3.5.8 → 3.5.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +9 -7
- package/dist/cli.js +74 -74
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -236,13 +236,15 @@ the gateway:
|
|
|
236
236
|
with signed thinking replay kept opaque to the client;
|
|
237
237
|
- unsupported semantics are rejected with field-level errors.
|
|
238
238
|
|
|
239
|
-
This is not a promise of full OpenAI or Anthropic parity.
|
|
240
|
-
|
|
241
|
-
|
|
242
|
-
|
|
243
|
-
|
|
244
|
-
|
|
245
|
-
|
|
239
|
+
This is not a promise of full OpenAI or Anthropic parity. The provider locally
|
|
240
|
+
enforces only a bounded `single-string-object-v1` JSON Schema profile for
|
|
241
|
+
one-shot text metadata requests: Responses `text.format` in compatible mode
|
|
242
|
+
(Codex thread titles) and Anthropic Messages `output_config.format` regardless
|
|
243
|
+
of `responses_fidelity_mode` (Claude Code session titles). Current tool
|
|
244
|
+
declarations are preserved, but output calls are rejected with an explicit
|
|
245
|
+
compatibility diagnostic. Arbitrary Structured Outputs, JSON mode, tool
|
|
246
|
+
histories, continuations, and strict-fidelity Responses use remain fail-closed;
|
|
247
|
+
this local envelope is not evidence that Kiro natively enforces JSON Schema. Hosted tools, background Responses,
|
|
246
248
|
Responses conversation objects, remote file references, exact input-token
|
|
247
249
|
counting, and destructive context edits are also outside the supported surface. The
|
|
248
250
|
[compatibility guide](docs/PROTOCOL_COMPATIBILITY.md) is the current contract;
|