feat(auto-drive): send requestedBytes in createPaymentIntent and handle credit cap rejection

[yeziR4]

Resolves #691

Overview

This PR updates createPaymentIntent in @autonomys/auto-drive according to the specifications in #691:

1. Input Validation: Added positive safe integer validation for sizeBytes, rejecting non-integers, <= 0, NaN, and Infinity with a clean TypeError instead of leaking internal BigInt errors.
2. requestedBytes Payload: Updated createPaymentIntent to send { requestedBytes: sizeBytes.toString() } in the POST /intents request body so server-side credit-cap checks can be performed prior to on-chain payment.
3. Structured Error Handling (CreditCapExceededError): Created and exported CreditCapExceededError (with code 'CREDIT_CAP_EXCEEDED') allowing callers to programmatically catch and branch on over-cap rejections. Parses JSON error response bodies to surface clean error messages rather than raw JSON strings.
4. Documentation: Updated docstrings to accurately document the request body and credit-cap error behavior.
5. Unit Tests: Added 7 unit tests in packages/auto-drive/__test__/payment.test.ts covering validation rules, payload structure, credit cap errors, and general error handling.

Verification

• yarn workspace @autonomys/auto-drive build compiles with 0 errors.
• Jest unit tests pass 7/7 green (packages/auto-drive/__test__/payment.test.ts).
• Formatted with Prettier per repository config.

[yeziR4]

Hi @EmilFattakhov

I've opened this PR to resolve #691 per your specifications:

• Enforced positive safe integer validation for sizeBytes, rejecting non-integers, <= 0, NaN, and Infinity with a clean TypeError.
• Updated createPaymentIntent to forward { requestedBytes: sizeBytes.toString() } with Content-Type: application/json in POST /intents so backend credit-cap checks are performed prior to on-chain payment.
• Created and exported CreditCapExceededError with code 'CREDIT_CAP_EXCEEDED' allowing callers to cleanly catch and branch on over-cap rejections, and parsing JSON error messages rather than leaking raw JSON strings.
• Updated docstrings to document the payload and error behavior.
• Added comprehensive unit test suite in packages/auto-drive/__test__/payment.test.ts (7/7 tests passing green).

Ready for review whenever you have time. Thank you

[yeziR4]

@jim-counter

[EmilFattakhov]

Thank you for your contribution @yeziR4! A couple of blocking comments that should be relatively easy to address.

[EmilFattakhov]

This only covers only covers the coded errors. Auto Drive's HttpError.handleResponse sends { error: <code>, message } when an error carries a machine-readable code, but { error: <the message> } — no message key — for every uncoded one.

[EmilFattakhov]

Unrelated reformat — please restore the one-member-per-line union.

[EmilFattakhov]

Deviates from convention, what's this module is used for? Please drop it unless there's a clear reason

[EmilFattakhov]

What would a nice addition: since #691 POST /intents also gained paymentMethod (usdc_eth), that would be great if you could include this as a part of that PR as well. Optional though, could be addressed separately.

[yeziR4]

Thanks for the review @EmilFattakhov! All review comments have been addressed in commit \575ab5eb:

1. Uncoded Error Response Handling: Updated error message extraction to check \parsed?.message || (typeof parsed?.error === 'string' && parsed.error !== 'CREDIT_CAP_EXCEEDED' ? parsed.error : body). This seamlessly supports both coded errors ({ error: , message }) and uncoded errors ({ error: }) from Auto Drive's \HttpError.handleResponse. Added an explicit unit test for uncoded responses.
2. Restored Union Formatting: Restored the one-member-per-line formatting for \PaymentIntentStatus.
3. Dropped \jest.config.js: Removed \packages/auto-drive/jest.config.js\ and dropped the package-level test script from \package.json\ to adhere to repo conventions.

Ready for review, thank you!