Contract badge-minter: add badge issuance summary and cooldown-grace accessor

[CMI-James]

Background

Contributors need implementation-ready contract backlog items so work can be picked up without reconstructing scope from scattered context.

Feature Focus

Add the contract read or workflow support described in the title.

Where to Implement (Exact Targets)

• contracts/badge-minter/src/lib.rs
• contracts/badge-minter/src/storage.rs
• contracts/badge-minter/src/types.rs
• contracts/badge-minter/src/test.rs

What to Implement

• Add the public read-only methods or supporting contract behavior described in the issue title.
• Return structured output that frontend and backend consumers can use directly.
• Handle empty, missing, paused, or not-yet-configured states explicitly.
• Preserve current contract mutation paths and storage invariants.

Interface / Endpoint / Method Details

• Prefer named response types over opaque tuples where practical.
• Reuse existing storage aggregates when possible instead of duplicating counters.
• Document fallback values, zero-state behavior, and any rounding conventions in generated docs.

Acceptance Criteria

• Consumers can retrieve the new state through stable contract reads or clearly defined public methods.
• Unknown ids and empty states return predictable results.
• Existing write flows remain backward compatible.

Required Tests

• Add unit tests for the main success path.
• Add coverage for at least one empty, blocked, or missing-state path.

Definition of Done

• The contract change is implemented and covered by tests.
• Generated contract docs remain in sync with the public interface.

[sadiqabubakar826-del]

@sadiqabubakar826-del has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer am active to resolve this issue, have gone through it and will carry out the task perfectly and diligently
Kindly assign this to me thanks

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

[nomsoscript]

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

Please can I fix this. I know what to do and do it fast. I'd submit a merge-able PR.

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

[drips-wave]

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

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