fix(client): forward error batch responses instead of parsing them - #1847

✅ No new issues found.

Reviewed changes — reviewed the full diff (2 files, 1 commit b97234dd) of fix(client): forward error batch responses instead of parsing them:

• batch.ts: a new early branch in executeBatch forwards any status >= 400 batch response as-is to every subrequest via mapSubresponse, wrapping the body in once(...) so one-shot bodies aren't consumed twice.
• batch.test.ts: three new tests covering buffered + streaming forwarding, single body resolution, and a regression check that status < 400 batches still parse.

I traced the change end-to-end and it's correct: an error response now flows through the StandardLink codec exactly like a non-batched request, where RPCLinkCodec.decodeResponse (status < 400 = isOk) turns it into a proper ORPCError with the original status/headers/body — which is precisely the reported bug fix. The once wrapper shares one body resolution across subrequests, and ClientPeer.close() rejects the still-pending peer.request promises, which the outer suppressErrorFromCurrentBatch guard swallows — so there's no hang, unhandled rejection, or double-resolution. The new tests genuinely fail without the fix (a string body is not an array/Blob/stream, so the old path threw Invalid batch response format.), and all 31 batch tests pass locally.

  ^{｜ View workflow run ｜ Using DeepSeek Flash (free via Pullfrog for OSS) ｜ 𝕏}