fix(tools): keep the forget-request timeout when a caller passes a signal

[Cintu07]

what breaks

forgetMemoryRequest (packages/tools/src/shared/forget-memory.ts) combined the caller's abort signal and the 30s fetch timeout with ??:

signal: options?.signal ?? AbortSignal.timeout(FETCH_TIMEOUT_MS),

so the two are mutually exclusive. Pass a cancellation signal and the request loses its timeout and becomes unbounded again, which reopens the hang #1451 set out to close. A caller that wants both cancellation and a timeout has no way to ask for it.

why it matters

It is latent today, because no production call site passes options (ai-sdk.ts:332 and openai/tools.ts:490 both omit it). It becomes a real hang the first time someone wires up cancellation.

the fix

Compose the two with AbortSignal.any instead of choosing between them, so the request aborts on whichever fires first:

signal: options?.signal
    ? AbortSignal.any([options.signal, AbortSignal.timeout(FETCH_TIMEOUT_MS)])
    : AbortSignal.timeout(FETCH_TIMEOUT_MS),

AbortSignal.any is available on the repo's Node 20 engines floor, Bun, and workerd.

verified

Updated the existing signal test in tool-operations.test.ts to assert the composed behavior: a composite signal (not the raw caller signal) that still aborts when the caller aborts. Full file is green:

vitest run src/tool-operations.test.ts  ->  14 passed

Closes #1549

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.