Recipient Share Lock During Dispute

[Kingsman-99]

Description

When a dispute is active, individual recipient shares should be lockable so a subset of recipients can still be paid while disputed shares remain frozen. This is more surgical than locking the entire invoice.

Technical Context

Add locked: bool to the RecipientShare struct in types.rs. Add lock_recipient_share(invoice_id, recipient: Address) and unlock_recipient_share admin-only methods to contracts/split/src/lib.rs. In release_payment, skip locked recipients and accumulate their shares in an UnreleasedFunds(invoice_id) storage key.

Acceptance Criteria

• release_payment skips recipients whose locked flag is true
• Locked share amounts accumulate under UnreleasedFunds(invoice_id)
• unlock_recipient_share followed by a separate release_locked_funds call releases them
• RecipientShareLocked and RecipientShareUnlocked events are emitted from events.rs
• Locking a recipient not in the invoice returns RecipientNotFound
• All CI checks (cargo build --target wasm32-unknown-unknown, cargo test, cargo clippy) pass and the branch has no merge conflicts

---

[DANTE-1903]

@DANTE-1903 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Please I would like to resolve this issue please assign it to me

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

[Sundayabel222]

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

Hi maintainer i would love to work on this

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@Sundayabel222's PR #548 was approved and merged by @Kingsman-99.

🏆 @Sundayabel222: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (592 total points). Track your full progress on GrantFox.

👏 Great work, @Sundayabel222! Keep contributing to Stellar-split.

[drips-wave]

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

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