Add unit tests for locked allocation get_locked_allocation returning claimed true after claim

[Chucks1093]

Summary

After a creator claims their locked allocation, get_locked_allocation should return a status with claimed: true. A unit test should confirm the field updates correctly after a successful claim and stays true if the view is called again.

Scope

• Register a creator with a locked allocation
• Advance ledger past the unlock ledger
• Claim the allocation
• Call get_locked_allocation and assert claimed is true
• Call again and assert it is still true

Acceptance Criteria

• claimed field is false before claim
• claimed field is true after successful claim
• Field remains true on subsequent reads

ETA: 12 hours

---

Coordinate on Telegram

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.

[aarogund]

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

I can work on this immediately. Kindly assign it to me.
Thanks.

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

[Alaka-ibr]

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

Hi maintainer, will love to work on this.

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

[drips-wave]

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

🧑‍💻 @Alaka-ibr: 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 marked as completed by a Drips Wave moderator for @Alaka-ibr as part of the Stellar Wave Program's 6th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor provided the requested unit and regression tests in PR #535, which specifically addresses the requirements of issue #485 in the file locked_allocation_claimed_view_regression.rs. The PR was merged by a maintainer, who confirmed the work was correct after making minor adjustments for upstream API compatibility.

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

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.