Download hellogrok-cli 0.1.34

Added
- Responses absorb window for retryable response.failed SSE terminals. While nothing has been written to the client, a Responses stream whose only terminal is a retryable failure (rate limit, concurrency, overload) is withheld — response headers and early frames stay buffered up to 32 frames — and replayed inside the absorb window with the same backoff and Retry-After handling as HTTP soft failures. Grok Build keeps its full retry budget; an exhausted window passes the failure through retryable. absorb_retry_max_secs = 0 streams the failed event immediately; deterministic response.failed events pass through without retry.
- Structured upstream error summaries for HTTP errors and Responses response.failed/error events (type, code, message), with bearer tokens, key assignments, and sk- values redacted and long messages truncated. An official Grok catalog name (for example grok-4.6) observed on a non-xAI custom channel is logged with body size, tool count, and session presence to aid /resume diagnosis; first-party api.x.ai routes and custom IDs without the grok- prefix are excluded.
- Explicit non-retryable 502 responses for stream-shape mismatches: an SSE body answered to a non-streaming request, or a streaming body answered to Grok Build's fixed non-streaming WebSearchClient request.
Fixed
- Concurrency-limit rejections (concurrency, concurrency limit, and the corresponding Chinese phrases) classify as transient, and error envelopes nested under response.error are recognized the same as top-level error objects.
- Client disconnects no longer surface as upstream stream failures. Messages, Chat Completions, native, and Responses streams log a client abort and emit no proxy_stream_error when the client write fails or the request context is canceled; truly truncated upstream streams still emit the error.
- Benign upstream-model mismatches log once per channel/protocol/configured/upstream pair (bounded to 256 keys); conflicting and invalid declarations always log. Responses SSE headers are sent only after the hold decision, so an absorbed retry never emits partial headers.