v0.1.40

Release Notes — v0.1.40

Shorter managed stall window, uniform across channels

• Managed inference_idle_timeout_secs lowered from 1800 to 900 seconds. The 30-minute ceiling traded too much failure-detection latency for stall tolerance. Fifteen minutes still covers twice DeepSeek's documented ten-minute queue and multiples of the observed three-minute relay stalls, and the downstream watchdog (deadline minus 30 seconds) already converts a true stall into a retryable proxy_stream_error, so the extra wait mostly delayed discovery.
• The managed timeout now applies to every proxied channel, including first-party api.deepseek.com routes. It is a resilience projection, not channel metadata, so it is no longer special-cased. Explicit per-model or global [models] values remain user-owned and win on every channel alike. The proxy's DeepSeek-specific 660-second upstream byte window is unaffected.

Restart both hellogrok executables after upgrading; the rewritten channel values take effect at the next proxy start. Channels you configured explicitly keep their value unchanged.

---

发布说明 — v0.1.40

托管停顿窗口缩短，且对所有渠道统一生效

• 托管 inference_idle_timeout_secs 从 1800 秒降为 900 秒。 30 分钟的上限为停顿容忍付出的失败感知延迟过高。15 分钟仍是 DeepSeek 文档排队上限（10 分钟）的 1.5 倍，也数倍于实测的 3 分钟中转停顿；而下游看门狗（时限减 30 秒）本来就会把真正的卡死转为可重试的 proxy_stream_error，多出的等待主要只是推迟了发现。
• 托管超时现在对所有代理渠道统一生效，包括 api.deepseek.com 官方路由。 它是韧性投影而非渠道元数据，因此不再被特判。显式的 per-model 或全局 [models] 值在所有渠道上同样保持用户所有且优先。代理对 DeepSeek 官方的 660 秒上游字节窗口不受影响。

升级后请重启两个 hellogrok 可执行文件；渠道改写值在下次代理启动时生效。你显式配置过的渠道保持原值不变。