fix: clean up abort listener after response lifecycle

[meaqua9420]

• I understand that this repository is auto-generated and my pull request may not be merged

Changes being requested

Fixes #1811.

This keeps the caller-provided AbortSignal listener long enough to preserve user abort behavior while the response body is still being consumed, then removes it once the response lifecycle has settled:

• fetchWithTimeout() now returns the Response plus an idempotent cleanup callback for the caller-signal listener.
• The SDK timeout is still cleared as soon as fetch resolves, preserving the current timeout behavior.
• Normal JSON/text parsing removes the caller listener after body parsing settles.
• Error-response body reads and retry/body-cancel paths run the same cleanup.
• SSE streams pass cleanup into Stream.fromSSEResponse() so the listener is removed when iteration finishes or is closed/broken.

Difference from existing PRs

I re-checked the existing PRs for #1811 before opening this one.

• Compared with the smaller one-line/fetch-settled fixes (fix: remove abort event listener on successful completion in fetchWithTimeout #1812, fix: remove abort listener on successful fetch to prevent Deno hang #1823, Fix abort listener cleanup in fetchWithTimeout #1828, fix(client): remove caller abort listener after successful fetch #1835, fix: remove abort event listener from caller signal after request completes #1858, fix: remove abort listener after fetch settles #1877, fix(client): remove abort listener on success in fetchWithTimeout #1893), this does not remove the caller listener immediately when fetch resolves. It keeps caller abort forwarding available while response body parsing is still in progress.
• Compared with fix: remove abort listener after fetch completion #1906, this does not keep the listener indefinitely for streaming responses. It wires cleanup into the SSE stream lifecycle so normal stream completion/break also removes the listener.
• Compared with broader timeout/body-read PRs such as fix: keep timeouts active through response body reads #1862/fix(client): keep request timeout armed across body-read phase #1826, this does not change timeout semantics to cover response body reads. It only scopes cleanup for the external caller AbortSignal listener.
• fix: clean up stream abort listeners #1884 addresses separate higher-level stream helper abort listeners; this PR is focused on the fetchWithTimeout() caller signal listener from fetchWithTimeout does not remove abort event listener on successful completion, preventing process exit on Deno #1811.

Additional context & links

The motivating Deno behavior is that a listener attached to AbortSignal.timeout() can keep the timeout timer ref'd until it fires. Removing the listener after successful body/stream completion lets successful requests exit promptly while still preserving abort behavior during body consumption.

Tests

• ./node_modules/.bin/jest tests/index.test.ts -t "caller abort listener|caller abort forwarding" --runInBand
• ./node_modules/.bin/jest tests/index.test.ts --runInBand
• ./node_modules/.bin/prettier --check src/client.ts src/core/streaming.ts src/internal/parse.ts tests/index.test.ts
• ./node_modules/.bin/eslint src/client.ts src/core/streaming.ts src/internal/parse.ts tests/index.test.ts
• git diff --check origin/master...HEAD
• ./scripts/build

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f49bf26187

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Preserve abort forwarding for binary responses

For __binaryResponse endpoints such as file downloads and audio speech, this finally runs immediately after returning the raw Response, before the caller has consumed response.body with blob(), arrayBuffer(), or a reader. Because fetchWithTimeout() only passes the SDK controller signal to fetch, removing the caller-signal listener here means aborting the user-provided signal during the subsequent binary body read no longer aborts the underlying response body; cleanup needs to be deferred until the returned Response is consumed/cancelled (or handled separately for raw responses).

Useful? React with 👍 / 👎.

[meaqua9420]

Fixed in dd0e115. Binary/raw responses now return a Response whose body is wrapped with the same idempotent cleanup callback, so the caller abort listener is not removed when the raw Response is handed back. It stays active until the binary body is consumed, cancelled, or errors, preserving caller abort forwarding during text()/arrayBuffer()/reader consumption while still removing the listener afterward. Added regression coverage for successful binary body consumption and abort during binary body reading.