Improvement: contract fuzz/invariant tests for check_claim and batch atomicity

[Psalmuel01]

Contracts have unit tests but no fuzz/invariant coverage of the trickier logic (threshold comparisons, batch all-or-nothing, expiry transitions).

Scope

• Add fuzz tests over check_claim threshold boundaries and trusted_issuers combinations.
• Add invariant tests: a batch either fully applies or fully reverts; a revoked or expired proof never reads valid; counters (if added) never go negative.
• Run in CI.

Value

Higher confidence in the security-critical read/write paths.

Acceptance

• Fuzz/invariant tests cover check_claim boundaries and batch atomicity, running in CI.

[Deevhyne1023]

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

Hi, I've looked into this issue and I'm confident I have the relevant experience to implement a proper solution that meets the acceptance criteria. I'd welcome the chance to take this on and can begin promptly once assigned, thank you

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

[Kappa16]

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

please maintainer ..pls assign this issue to me...i beg of you expect pr asap

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

[solidsole]

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

PLEASE maintainer... assign this issue to me ... I'm begging....

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

[ugoocreates-pixel]

@ugoocreates-pixel 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 because am software engineer and am capable of completing this task effectively.

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

[felladaniel36-hash]

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

let me work on this

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

[Devadakene]

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

I am experienced enough to implement this issue having worked on similar issues in the past. Please assign

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

[AGWAM001]

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

ill love to work on this immediately after being assigned

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

[drips-wave]

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

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