fix(telegram): only suppress EADDRNOTAVAIL in forceFallback, preserve timeout/network fallback

lzyyzznl · lzyyzznl · commit e9063f3a1f90 · 2026-06-24T17:57:08.000+08:00
ClawSweeper P1: the original forceFallback used the full
shouldUseTelegramTransportFallback classifier, which rejected
probe timeout/network errors (no 'fetch failed' + codes) that
still need IPv4 fallback promotion.

Fix: collect codes from the error and only check
isLocalSocketAllocationError(codes) — EADDRNOTAVAIL. All other
errors continue to promoteStickyAttempt as before.
diff --git a/extensions/telegram/src/fetch.ts b/extensions/telegram/src/fetch.ts
@@ -883,10 +883,14 @@ export function resolveTelegramTransport(
     sourceFetch,
     dispatcherAttempts: transportAttempts.map((attempt) => attempt.exportAttempt),
     forceFallback: (reason: string, err?: unknown) => {
-      if (err !== undefined && !shouldUseTelegramTransportFallback(err)) {
-        return false;
+      if (err !== undefined) {
+        const codes = collectErrorCodes(err);
+        if (isLocalSocketAllocationError(codes)) {
+          return false;
+        }
       }
-      return promoteStickyAttempt(stickyAttemptIndex + 1, new Error("forced fallback"), reason);
+      promoteStickyAttempt(stickyAttemptIndex + 1, new Error("forced fallback"), reason);
+      return true;
     },
     close,
   };
