Add an unwrap-free assert_some helper

[Baskarayelu]

Summary

Returns typed error if Option is None, used in entrypoints to avoid panics.

Background

This change improves the day-to-day experience for the people who consume this code (operators, downstream contracts, frontend engineers, support). It is not a strict bug, but the current behaviour forces workarounds and the proposed change removes them.

Acceptance criteria

• The change matches the summary above.
• No regression in the existing test suite.
• The change is documented where it is observable (README, docs/, public API reference).
• Lint, type-check, and tests all pass locally.
• PR description references this issue with Closes #<this-issue>.

Implementation hints

• Keep the public API surface backwards-compatible if possible. If a breaking change is unavoidable, document the migration step.
• Land any new constant in a single place (config/, consts.rs, or the equivalent) and re-use it everywhere.
• Update the relevant docs/ page in the same PR so reviewers see the docs change together with the code change.
• Add or update the corresponding test so the new behaviour is locked in.

Repo-specific notes

• This is a Soroban contract crate. Run cargo build --target wasm32-unknown-unknown --release to verify the change still builds for WASM.
• Run cargo test -p <package> for the affected crate, and cargo clippy --workspace --all-targets -- -D warnings before pushing.
• Keep #![no_std] discipline: do not introduce std:: calls; use soroban_sdk primitives.

Out of scope

• Unrelated refactors in adjacent files.
• Stylistic-only changes (formatting, renaming) that are not required by the fix.
• Anything beyond the acceptance criteria above; surface follow-ups as separate issues.

How to claim and submit

1. Comment on this issue saying you'd like to take it on; wait for a maintainer to assign you (avoids duplicated effort).
2. Open a PR that references this issue (Closes #<this-issue>).
3. Make sure CI is green and request review from a CODEOWNERS maintainer.
4. PRs that close this issue and pass review may qualify for a reward — see the MAYBE REWARDED label and the GrantFox OSS campaign page.

---

Category: enhancement  ·  Campaign: GrantFox OSS · Official Campaign · Maybe Rewarded

[smog123]

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

i will like to work on this issue

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

[drips-wave]

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

🧑‍💻 @smog123: 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 campaign!

@smog123's PR #1654 was approved and merged by @Baskarayelu.

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

👏 Great work, @smog123! Keep contributing to QuickLendX.

[drips-wave]

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

😎 @smog123: You earned 100 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.