Add regression coverage for RPC retries, fee quotes, and chain interactions in `src/starknet/client.ts`

[Jagadeeshftw]

Description

The behavior is close to correct, but the repo does not lock the edge cases down yet. src/starknet/client.ts owns RPC retries, fee quotes, and chain interactions, but the current behavior does not yet define the contract tightly enough for safe maintenance. Design the change so the runtime path, tests, and docs all describe the same behavior.

Requirements and context

• Keep the contract specific to src/starknet/client.ts and its existing callers.
• Add coverage for the success path and the failure or boundary path relevant to this issue.
• Preserve compatibility where older callers or existing tests already rely on the current shape.
• Keep the change easy to review and small enough for one focused PR.

Suggested execution

Fork the repo and create a branch

git checkout -b starknet-client-regression-182

Implement changes

• Update/Write: src/starknet/client.ts
• Write comprehensive tests: src/starknet/client.test.ts
• Add documentation: docs/starknet/client.md
• Keep any new helper names consistent with the rest of src/

Test and commit

• Run pnpm test
• Run pnpm lint
• Add a note for any edge cases that are intentionally out of scope

Example commit message

test: add regression coverage for edge cases

Guidelines

• WCAG 2.1 AA is not relevant here; keep the focus on correctness and maintainability.
• Prefer a narrow, well-documented fix over a broad refactor.
• Timeframe: 96 hours

[Cyberking99]

@Cyberking99 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello, please can I take this?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Cyberking99 to this issue.

[Jagadeeshftw]

Thanks for applying here. Please also join our Telegram group here: https://t.me/+vTbe0hOUKrFhNTJl. It helps us keep communication clear while we review contributions.

[drips-wave]

Congratulations, @Cyberking99! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Cyberking99: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

Congratulations, @Cyberking99! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Cyberking99: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊