[kudala-bharani]

Summary

Responses rejected by their Content-Length left the unread body open. Start cancelling that body and return PROVIDER_RESPONSE_TOO_LARGE without waiting for cleanup to settle. Cleanup rejection is handled without replacing the known size failure.

Related issue

Closes #39

Changes

• Start cancellation on the early size rejection; tolerate absent bodies, pending cleanup, and cleanup errors.
• Add regression coverage for successful, rejected, and pending cancellation, plus a response without a body. Document the cleanup behavior.

Validation

• npm run check
• npm run check:generated
• npm test — 60 passed
• Additional validation is described below, or was not needed.

Additional validation: The cancellation tests failed before the fix because the callback was never called. The pending-cancellation test also fails if cleanup is awaited: it verifies that generation completes while cancellation remains pending, without a wall-clock timeout. npm run test:release passed all 4 tests, and npm run test:package verified the installable package. Local validation used Node.js 25.9.0.

Risk and compatibility

• Security or permission effects: Cleanup is attempted for rejected responses; provider contents and cleanup errors are not exposed in results.
• Compatibility or breaking changes: None. Public failure codes, response-size limits, and timeout handling are unchanged.

Checklist

• This change is focused on one issue.
• Behavioral changes include tests.
• User-facing behavior and unsupported constructs are documented.
• Generated files are current.
• No credentials, private data, or unredacted model output are included.
• Commits include the required DCO Signed-off-by line.

[haseebahmed248]

Thanks for the focused fix and tests. The type checks, generated-contract check and all 59 tests pass, and CI is green. Catching the cleanup error is appropriate here because it must not replace the known size failure. There is one pending-cancellation case to address, noted inline.