fix(cache): settle Cache.add/addAll for responses with a body

[edenbuilds]

Summary

• Cache.add / Cache.addAll hung forever when the response had a body (204/no-body settled fine).
• Root cause: fetchFinale attaches stream.finished() for end-of-body, but undici body streams are pull-driven — with no consumer, the stream never finishes and processResponseEndOfBody never resolves the waiters (issue Cache.add() and Cache.addAll() never settle for a response with a body #5615).
• Fix mirrors Cache.put: clone the response, fully read the original stream (unlocks end-of-body), set body.source on the clone for storage.

Test plan

• New regression: node --test test/web/cache-add-body.js
• Manual repro from Cache.add() and Cache.addAll() never settle for a response with a body #5615 settles and cache.match returns body text
• CI on PR

Made with Cursor

[KhafraDev]

If, as the issue OP suggested, it is caused by #3093, then the fix is to revert that, not some crummy ai slop.

[edenbuilds]

Thanks, I checked this against current main and reproduced the tradeoff. I refreshed a local copy onto current main (the fork branch was 96 commits behind): restoring the #3093 transform-stream path by itself still leaves the new body-bearing cache.add() regression pending, while retaining the current cache workaround makes the subsequent cache.match() fail because the stored response stream is locked. I have not pushed a speculative revert that would leave either path broken. The remaining fix needs a targeted cache/fetch integration shape, or confirmation that you want the broader #3093 revert despite that regression.

[KhafraDev]

#5844 is an actual fix. Please don't send another ai generated response.