Add configurable half-open probe request count to CircuitBreaker

[Kingsman-99]

Description

CircuitBreaker transitions directly from open to closed after a reset timeout, without a half-open probe phase. If the downstream service is still degraded, the circuit immediately re-opens after a flood of requests.

Acceptance Criteria

• Constructor accepts halfOpenProbeCount (default 1)
• In half-open state, only halfOpenProbeCount requests are allowed through
• All probes succeeding closes the circuit; any probe failing re-opens it immediately
• Unit tests pass

Context

• Target file: src/resilience/CircuitBreaker.ts
• Probes beyond halfOpenProbeCount are rejected with a CircuitOpenError in half-open state

[ValJnr-dev1]

@ValJnr-dev1 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer,

I’m a smart contract and full-stack developer and would love to contribute to this issue. I’m an experienced contributor with hands-on expertise in Rust, Soroban, Cairo, and TypeScript.

I’m passionate about building secure, scalable blockchain solutions, with a strong emphasis on writing clean and maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 24 hours of assignment.

I’d greatly appreciate the opportunity to contribute and help move this forward.

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

[quickweb-stack]

@quickweb-stack has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I've reviewed the issue and understand the requirements. I'd love to work on this and submit a clean PR that meets the acceptance criteria.

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

[Dev-sandy1]

@Dev-sandy1 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Good day can i work on these.

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

[drips-wave]

Congratulations, @Dev-sandy1! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Dev-sandy1: 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 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@Dev-sandy1's PR #789 was approved and merged by @Kingsman-99.

🏆 @Dev-sandy1: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (322 total points). Track your full progress on GrantFox.

👏 Great work, @Dev-sandy1! Keep contributing to Stellar-split.

[drips-wave]

This issue has been completed by @Dev-sandy1 as part of the Stellar Wave Program's 8th Wave 🥳

😎 @Dev-sandy1: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.