[eknathdj]

Fixes #413

With overrideGlobalObjects: false, a handler that returns a Response whose
body stream errors before its first chunk is answered with a complete, empty
200 (Content-Length: 0). That is the reporter's repro, and it is easy to hit
in a gateway: a failing upstream turns into an empty success the client cannot
tell from a real one.

The early read in responseViaResponseObject wraps the read in
readWithoutBlocking(...).catch(...), and the catch sets done = true. That
flag means "the body has ended", so a read error was being treated as a clean
end of body — the response was written with Content-Length: 0 and ended
normally. With the default overrideGlobalObjects: true the same body cuts the
connection instead.

The fix records the error rather than treating it as end-of-body, and breaks out
of the early read when one happens. The rejected read is then handed to
writeFromReadableStreamDefaultReader, which destroys the connection — the same
teardown the default path already uses.

Verification

The reporter's repro, run against the built package on Node 24:

• before: 200, content-length: 0, complete: true, empty body
• after: the request errors with aborted (connection cut)

The new test in test/listener.test.ts covers this and fails on main without
the source change. It uses a captured native Response because the
overrideGlobalObjects block earlier in that file replaces globalThis.Response.

Full suite: 497 passed, 2 failed, 5 skipped. The two failures are the
/readable-stream chunk-boundary assertions in test/server.test.ts, which fail
the same way on unmodified main and are unrelated to this change.