@sunerpy/kiro-provider 0.8.0 → 0.8.1
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 +6 -3
- package/dist/cli.js +65 -63
- package/package.json +7 -1
package/README.md
CHANGED
|
@@ -564,8 +564,10 @@ Standard clients must also stay within the verified subset. In safe mode a
|
|
|
564
564
|
client that always sends system/developer instructions, custom grammars,
|
|
565
565
|
namespace tools, or Anthropic `cache_control` receives a field-level 400; the
|
|
566
566
|
gateway does not modify that request to force it through Kiro. The optional
|
|
567
|
-
`legacy-user-prefix` projection is
|
|
568
|
-
|
|
567
|
+
`legacy-user-prefix` projection is an explicit instruction-only compatibility
|
|
568
|
+
mode. It remains deprecated, but removal is evidence-gated: Kiro must expose a
|
|
569
|
+
protocol-faithful native instruction channel, or affected clients must migrate
|
|
570
|
+
away from instruction roles first.
|
|
569
571
|
|
|
570
572
|
The default `session_affinity_mode: "explicit-only"` never hashes prompt text
|
|
571
573
|
to guess a conversation. Responses checks, in order,
|
|
@@ -665,7 +667,8 @@ returns `unsupported_instruction_projection` and never rewrites the request.
|
|
|
665
667
|
Set Zuno `options.maxTokens` to `null` as shown so its generic layer does not
|
|
666
668
|
add the unsupported `max_output_tokens: 32000`. Neither setting uses a private
|
|
667
669
|
Header or client-side prompt patch; the legacy mode is an explicit migration
|
|
668
|
-
exception
|
|
670
|
+
exception whose removal is gated on native instruction fidelity or completed
|
|
671
|
+
client migration.
|
|
669
672
|
|
|
670
673
|
## Use with Codex CLI
|
|
671
674
|
|