GPT-5 finding
AbortSignal listener added during backoff can leak if not aborted
lowmaintainabilitymedium
- src/providers/orchestrator.ts:323-329
The abort listener is registered with `{ once: true }` so it cleans itself up on abort, but if the backoff completes normally (no abort), the listener remains attached to the signal. With few retries this is small, but over many orchestrations it is a minor leak.
Recommendation
Capture the listener and remove it after the timer fires (in the resolve path) if an AbortSignal was provided and did not abort.