evanfang0054 adc0a89f13 fix(feishu): honor NO_PROXY before proxying the long connection ... webSocketProxyUrl() picks up https_proxy/HTTPS_PROXY/http_proxy/ HTTP_PROXY and forces the Feishu WSS long connection through the proxy, without consulting NO_PROXY/no_proxy. With a local proxy exported in the shell (Clash/V2Ray setups), every long-connection attempt is rejected by Feishu's server and the runtime force-closes and retries in a loop, so the bot never reaches a stable connected state. Resolve NO_PROXY/no_proxy for the long-connection endpoints (open.feishu.cn / open.larksuite.com) before falling back to the proxy env: exact host, parent-domain (.cn, feishu.cn) and * entries follow the common NO_PROXY semantics. - production.mjs: NO_PROXY gate in front of the proxy lookup - feishu-proxy.test.mjs: NO_PROXY exclusion and fallthrough cases - lib/index.js: regenerated host bundle		2026-09-01 09:46:49 +08:00
..
connection-supervisor.mjs	fix: complete per-bot agent preset lifecycle	2026-08-22 00:20:23 +08:00
controller.mjs	Internalize all IM channel implementations	2026-08-15 15:40:53 +08:00
credential-store.mjs	Internalize all IM channel implementations	2026-08-15 15:40:53 +08:00
index.mjs	feat: add stable proactive delivery	2026-08-30 11:24:53 +08:00
production.mjs	fix(feishu): honor NO_PROXY before proxying the long connection	2026-09-01 09:46:49 +08:00
rpc.mjs	feat: add message source context enhancement	2026-08-29 10:46:06 +08:00