Bound recovery.rs RecoveryStorage history growth and add prune entrypoint

[greatest0fallt1me]

Description

RecoveryStorage in recovery.rs persists MarketRecovery records for emergency procedures, but unbounded recovery history grows persistent storage and rent cost over time. Add an upper bound on retained recovery records per market plus an admin prune entrypoint, mirroring the existing event-archive pruning.

Requirements and Context

• Cap retained recovery records in contracts/predictify-hybrid/src/recovery.rs.
• Add an admin-gated prune function (with require_auth) and expose it via lib.rs.
• Ensure pruning never removes the active recovery state of an unresolved market.
• 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/recovery-history-bounds

2. Implement changes
   • contracts/predictify-hybrid/src/recovery.rs, contracts/predictify-hybrid/src/lib.rs
3. Test and commit
   • cargo test -p predictify-hybrid -- recovery
   • Cover edge cases: prune with active recovery present, prune count > stored
   • Include test output and notes in the PR

Example commit message

feat: bound recovery history and add admin prune

Acceptance Criteria

• Recovery history is capped per market
• Admin prune requires auth and preserves active recovery state
• Storage growth is bounded under repeated recovery events

Guidelines

• Minimum 95% coverage on touched code, validate auth and storage growth bounds
• Clear documentation and inline comments
• Timeframe: 96 hours

[Dopezapha]

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

Hey maintainer, I would love to work on this issue. Kindly assign the issue to me. Thanks

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

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @Dopezapha as part of the Stellar Wave Program's 5th Wave 🥳

😎 @Dopezapha: 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.