Changed
fetchintercept no longer does sync I/O on the response hot path. ReplacedwriteFileSyncwithfs/promises.writeFileso writing the captured request file never blocks the event loop atmessage_start. The scan branch of the tee'd response now cancels itself right after writing the request file instead of draining the stream to EOF, removing any backpressure coupling between the scan branch and the caller's branch for the rest of the response. Request body extraction now runs concurrently with the outbound fetch rather than gating it. The wrappedResponsealso strips the upstreamcontent-lengthheader to avoid runtimes/proxies second-guessing the re-wrapped stream. Hygiene changes — no behavior change and none of these were shown to cause user-perceptible latency, but sync I/O inside afetchinterceptor is a footgun worth removing.