zevairouter 1.0.252 → 1.0.254

package/cli/app/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Unreleased
 
+# v1.0.254 (2026-08-19)
+
+## Performance
+- **Kiro requests can finally hit the upstream prompt cache.** Kiro/CodeWhisperer caches on an exact prefix match, and two things guaranteed a miss on every turn: `conversationId` was a fresh `uuidv4()` per request (so each turn looked like a brand-new conversation), and the volatile `[Context: Current time is …]` marker was prepended to the *first* user message (so msg0 changed every second and the prefix never matched again even within one conversation). Added `kiroSessionReplay` (ported from 9router, adapted): the first user message is frozen per session and replayed byte-identically on later turns, while the timestamp is applied to the live turn only. Since no conversation id arrives from the client, one is derived deterministically from connection + opening message. The frozen msg0 also carries the tool specs, so the cache key includes a tool fingerprint — a changed toolset invalidates the entry instead of shipping stale specs. Verified across three turns: `conversationId` stable, msg0 byte-identical, timestamp present only on the current message.
+
+# v1.0.253 (2026-08-19)
+
+## Features
+- **Translators can now register a direct `source:target` route, skipping the OpenAI pivot.** Native-to-native pairs (e.g. `claude:kiro`) previously round-tripped through OpenAI, which has to flatten provider-native blocks into OpenAI messages and rebuild them — the lossy step behind several recent tool-call fidelity bugs. When a translator is registered for the exact pair it is used in a single hop, on both the request and response side. Guarded to pairs where neither side is OpenAI, since a single registry hop already *is* the direct route and routing it here would skip the OpenAI-intermediate request log.
+
+## Fixes
+- **Claude extended-thinking requests no longer vanish in translation.** `claudeToOpenAIRequest` built its result from scratch and never copied `body.thinking`, so any provider reached through the `claude→openai→X` pivot lost the request entirely: Kiro never saw its `<thinking_mode>` trigger even when the client explicitly asked for thinking, and OpenAI-shaped providers got no `reasoning_effort`. Enabled thinking now maps to `reasoning_effort`, scaled by `budget_tokens` using the same thresholds `antigravity-to-openai.js` already applies. An explicit `type: "disabled"`, or no `thinking` field, still yields nothing.
+- **Kiro tool calls no longer break on MCP tool names.** Kiro/CodeWhisperer only accepts names matching `[a-zA-Z0-9_-]{1,64}`, which MCP tools routinely violate (`tool with spaces`, `mcp__srv__do.thing`, names over 64 chars) — an invalid spec makes Kiro reject the entire request. Names are now sanitized (invalid characters collapsed to `_`, trimmed to 64, de-duplicated) across both the tool specs and the `toolUses` in history, so a history entry always refers to a tool Kiro was actually given. The reverse map travels as a non-enumerable `_toolNameMap` and `kiro-to-openai` restores the client's original name, so a renamed call still matches the client's declaration instead of being silently dropped.
+
 # v1.0.252 (2026-08-19)
 
 ## Fixes

package/cli/app/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zevairouter",
-  "version": "1.0.252",
+  "version": "1.0.254",
   "description": "Self-hosted AI router: many providers, one OpenAI-compatible /v1 endpoint and dashboard",
   "bin": {
     "zevai": "cli/cli.js"

package/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zevairouter-cli",
-  "version": "1.0.252",
+  "version": "1.0.254",
   "private": true,
   "description": "ZevaiRouter CLI - Start and manage ZevaiRouter server",
   "bin": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zevairouter",
-  "version": "1.0.252",
+  "version": "1.0.254",
   "description": "Self-hosted AI router: many providers, one OpenAI-compatible /v1 endpoint and dashboard",
   "bin": {
     "zevai": "cli/cli.js"