Add contract test: create_streams_batch() rejects a dust/zero-rate stream entry

[Austinaminu2]

Description

`test_dust_stream_rejected`/`test_dust_stream_with_cliff_rejected` cover the single `create_stream` path only. The identical dust-amount guard in the batch path (`lib.rs:561-563`) has no test.

Task

Add a batch-create test with one entry that would produce a dust/zero-rate stream, asserting the batch is rejected the same way the single-stream path is.

Good for contributors because

Mirrors an existing, well-understood single-stream test — mostly a matter of adapting it to the batch API.

[Michael997glitch]

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

I’ve resolved similar problems in the past and am confident I can implement a clean, efficient fix quickly,if am given the opportunity.

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

[nobodieair]

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

I'd like to work on this one if it's still available. Happy to be assigned. Deliver ASAP

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

[adelekevictor12]

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

Hello Maintainer, i can fix this issue

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

[Sureplus30]

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

I would like to work on this issue kindly assign me to this issue

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

[Digitalasu]

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

Hello, I'm interested in contributing to this issue and would appreciate the opportunity to work on it. Thank you

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

[soma-enyi]

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

Hi team, I'd like to work on this issue. I'm a full-stack developer experienced in TypeScript, Rust, and smart contract development across EVM and Soroban/Stellar ecosystems. I've built and shipped production systems covering backend APIs, frontend interfaces (Next.js, React), CI/CD pipelines, and onchain protocols — so I'm comfortable working across whatever layer this issue touches. My approach I'll start by reproducing the issue locally and reading the surrounding code to understand context and constraints. I'll scope the fix tightly to avoid unnecessary churn, write or update tests to cover the change, and make sure linting, formatting, and existing CI checks all pass before opening a PR. If anything in the issue is ambiguous, I'll flag it early rather than guess. What you can expect A single clean PR with a clear description linking back to this issue. Minimal, well-tested changes that follow the project's existing conventions. Fast turnaround — I'm available to start immediately and responsive to review feedback. Happy to discuss the approach further if needed. Looking forward to contributing.

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

[drips-wave]

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

🧑‍💻 @soma-enyi: 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 🌊