zevairouter 1.0.261 → 1.0.263

package/cli/app/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Unreleased
 
+# v1.0.263 (2026-08-21)
+
+## Fixes
+- **Antigravity streams now always finish with a valid OpenAI terminal chunk.** Antigravity can end with a candidate-less `usageMetadata` wrapper or a clean EOF instead of putting `finishReason` on the last candidate. The translator discarded that usage-only wrapper and returned nothing during flush, while the shared finalizer still emitted `[DONE]`; strict clients then failed with `OpenAI completions stream closed before a finish_reason was received`. Candidate-less usage is now retained, a missing clean terminal emits exactly one `stop` (or `tool_calls`) before `[DONE]`, and explicit Gemini reasons map to OpenAI's enum (`MAX_TOKENS` → `length`, safety reasons → `content_filter`) instead of leaking invalid values such as `max_tokens`.
+- **Antigravity streamed tool calls now preserve the exact client-declared name.** Tool names were sanitized to Gemini's identifier grammar without a reverse map or collision handling, so `a/b` and `a b` both became `a_b`; the model could call a different/ambiguous name that the client never declared. Antigravity request translation now allocates deterministic unique names across both Gemini- and Claude-backed models, rewrites call/response history consistently, leaves valid names untouched, and restores each original name on the streamed response.
+
+# v1.0.262 (2026-08-19)
+
+## Fixes
+- **Closing the Codex or xAI login modal never shut down its callback proxy.** `OAuthModal` fires `POST /api/oauth/{codex,xai}/stop-proxy` with no body when the modal closes, but the route parsed the JSON body before it looked at the action, so an empty body answered `400` and the `stop-proxy` branch was never reached. `stopCodexProxy()` therefore never ran: the loopback listener on `127.0.0.1:1455` stayed up until its 5-minute timeout, and reopening the modal inside that window hit `EADDRINUSE` and silently fell back to the legacy redirect path. A bodyless POST is now valid for `stop-proxy` only; every other action still requires a body, and `stop-proxy` still rejects providers that have no fixed-port proxy. Trae/Windsurf/Zed were unaffected because they call the same action over GET.
+- **Buttons stopped looking clickable.** Tailwind v4 drops the default `cursor: pointer` on `<button>`, and the rule that used to restore it was lost, so controls rendered with the plain arrow. Measured on a live dashboard: 13 of 26 enabled buttons on the providers page had `cursor: default`, including the theme toggle, the language switcher and the collapsed nav section headers — icon-only controls that have no label or button chrome to signal affordance on their own. Restored globally for `button`, `[role="button"]`, `label[for]`, `summary` and `select`, plus `cursor: not-allowed` for disabled controls, which was also missing. Verified across three pages: 141 enabled buttons now report `pointer` and 10 disabled ones report `not-allowed`.
+
 # v1.0.261 (2026-08-19)
 
 ## Fixes

package/cli/app/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zevairouter",
-  "version": "1.0.261",
+  "version": "1.0.263",
   "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.261",
+  "version": "1.0.263",
   "private": true,
   "description": "ZevaiRouter CLI - Start and manage ZevaiRouter server",
   "bin": {

package/package.json

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