Dudu-0223 760bc9aa6a fix: scope timeoutOf by deadline code so nesting composes (codex round 2) ...

Round 2 P2: timeoutOf() accepted ANY TimeoutReason, so under nesting — when
the upstream handed to deadline() is itself a deadline (the RFC's named
tools/execute middleware follow-up) and its outer timer fires first —
AbortSignal.any preserves the outer reason and the inner bash/web would report
the outer timeout as their own (timedOut / WEB_FETCH_TIMEOUT) though their local
timer never expired. Add an optional code to timeoutOf; bash and web pass their
own code, so a foreign timeout falls through to the upstream-cancel path.

2026-07-06 17:07:11 +08:00

..

timeout.spec.ts

fix: scope timeoutOf by deadline code so nesting composes (codex round 2)

2026-07-06 17:07:11 +08:00