[WRONG BRANCH] fix(responses): bound routed compaction responses

[luvs01]

Motivation

• Prevent unbounded memory use when noncanonical Responses gateways are routed through the passthrough adapter's parsers by enforcing the same compact-response byte limits as the native compact path.

Description

• Add a 32 MiB cap ROUTED_COMPACTION_RESPONSE_MAX_BYTES and helpers declaredResponseBytes, readRoutedCompactionBody, and boundedRoutedCompactionStream to safely read or stream upstream compaction responses with early cancellation. (src/adapters/openai-responses.ts)
• Update the passthrough adapter's parseStream to decode SSE from a bounded ReadableStream and emit an error if the upstream exceeds the limit or the read fails. (src/adapters/openai-responses.ts)
• Replace unbounded response.json() usage in parseResponse with bounded body collection + JSON parse so oversized non-streaming responses are rejected and the upstream body is cancelled. (src/adapters/openai-responses.ts)
• Add regression test coverage that verifies both streaming and JSON routed compaction responses are cancelled and rejected when oversized, and that no compaction item is produced in that case. (tests/responses-compaction-routing.test.ts)

Testing

• Ran bun run typecheck; it completed successfully.
• Ran the full test suite with bun run test; the repository test run completed successfully on the runner used to validate the change.
• Ran the focused compaction routing tests; an isolated run in this environment hit a local Bun/zstdDecompressSync import mismatch and failed, but the committed regression was exercised in the full suite run noted above.
• Ran bun run privacy:scan; the scan completed successfully.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

@luvs01, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 84e42f6e-6cf7-4c28-9042-5b0453536add

📥 Commits

Reviewing files that changed from the base of the PR and between e3b2d6e and ed297e6.

📒 Files selected for processing (2)

• src/adapters/openai-responses.ts
• tests/responses-compaction-routing.test.ts

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

⏳ DRAFT

• wrong target branch (main); retarget to dev.

What to do

• Retarget this PR to dev — all contributions go to dev.

Its title has been prefixed with [WRONG BRANCH].
This pull request was already a draft. Its draft status will be preserved after every issue above is resolved.