Add per-milestone claim allowing incremental release of verified milestones in accountability_vault

[1nonlypiece]

Add per-milestone claim allowing incremental release of verified milestones in accountability_vault

Description

claim in contracts/accountability_vault/src/lib.rs only releases funds when all milestones are verified. Add claim_milestone(index) that releases that milestone's amount to success_destination as soon as it is verified, tracking released milestones to prevent double-claims. The vault transitions to Completed only after the last milestone is claimed.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Add claim_milestone with per-milestone released tracking in contracts/accountability_vault/src/lib.rs
• Prevent double-claiming the same milestone
• Transition to Completed only when all milestones are released
• Add incremental-claim tests in contracts/accountability_vault/src/test.rs

Suggested execution

• Fork the repo and create a branch
• git checkout -b feat/per-milestone-claim
• Implement changes
  • Modify contracts/accountability_vault/src/lib.rs
  • Add tests in contracts/accountability_vault/src/test.rs
  • Document incremental release in contracts/README.md
  • Add double-claim guards
• Test and commit
  • Run tests, cover edge cases
  • Include test output and notes

Example commit message

feat: add incremental per-milestone claim

Guidelines

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 96 hours

[Windowlight]

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

I’m interested in this issue and believe my experience with contracts, backend systems, and frontend implementation makes me a good fit. Happy to provide updates as I work through it.

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

[drips-wave]

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

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