Revenue pool: add pausable circuit-breaker for distribute and batch_distribute

[greatest0fallt1me]

Description

The vault has a pause circuit-breaker but RevenuePool does not. If a compromised admin key or buggy backend triggers erroneous distributions, there is no on-chain way to freeze outflows. Add pause/unpause/is_paused gating distribute and batch_distribute, mirroring the vault's pattern.

Requirements and Context

• Add Paused storage key and admin-gated pause/unpause with pause_set events.
• Block distribute and batch_distribute while paused; allow admin rotation while paused.
• Add is_paused() view defaulting to false.
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested Execution

1. Fork the repo and create a branch

   git checkout -b feature/revenue-pool-pause

2. Implement changes
   • contracts/revenue_pool/src/lib.rs — pause state + gating + events
   • SECURITY.md — document the new circuit-breaker
3. Test and commit
   • cargo test -p callora-revenue-pool
   • Test distribute-while-paused reverts; unpause restores
   • Include test output and notes in the PR

Example commit message

feat: add pause circuit-breaker to revenue pool

Acceptance Criteria

• pause/unpause/is_paused implemented and admin-gated
• Distributions blocked while paused
• Pause events emitted
• Tests cover paused/unpaused transitions

Guidelines

• .rs under contracts/revenue_pool/src/, cargo test, /// docs, minimum 95% line coverage, no unwrap() in prod paths
• Clear documentation and inline comments
• Timeframe: 96 hours

[wavyboy-build]

@wavyboy-build has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Let me work on this issue

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

[Richardkingz2019]

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

I am interested in working on this issue and i shall deliver qualitatively and promptly on this

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

[drips-wave]

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

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