[SC-70] contrib's insurance.rs and lease.rs — its only genuinely compiled, contrib-specific logic — have zero dedicated tests

[yusuftomilola]

Overview

contrib/src/insurance.rs (199 lines) and lease.rs (137 lines) are both genuinely declared in lib.rs's module tree (mod insurance; mod lease;) and are the only business logic in the crate beyond the base asset registry that actually compiles — but contracts/contrib/src/tests/mod.rs only declares asset_registry_tests plus the four modules flagged as uncompiled in [SC-61]. There is no test file for insurance or lease at all, despite them being real, live, deployed functionality.

Tasks

• Add tests/insurance.rs covering policy creation, claim filing (file_claim/whatever the entrypoint is named), and claim status transitions (ClaimStatus, imported by events.rs).
• Add tests/lease.rs covering lease creation, the lease lifecycle referenced by lease.rs's .expect("Lease not found") call sites (see [SC-59]), and expiry handling.
• Declare both new modules in tests/mod.rs.

Acceptance Criteria

• contrib's only real business logic beyond the base registry — insurance and lease — has dedicated test coverage.

Notes for Contributors

Requires Rust + Soroban. Workspace: contracts/ (soroban-sdk 23, members: assetsup, contrib, multisig-wallet, multisig-transfer, asset-maintenance). Run cargo test --all, cargo fmt --all -- --check, and cargo clippy --all-targets --all-features -- -D warnings before opening a PR — CI enforces all three. Comment below to be assigned.

[pameladelapito63-maker]

@pameladelapito63-maker has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Interested in working on this. I'll ensure the implementation is clean, tested, and aligned with project standards.

I'd love to work on this issue. I'll keep the implementation simple, clean, and well-tested.

I understand the expected outcome and would love to work on this. I'll provide a solution that satisfies the acceptance criteria.

I'd be glad to handle this issue. I'll keep the implementation concise, maintainable, and well-documented.

I've reviewed the issue thoroughly and can start working on it right away. Looking forward to contributing

Interested in working on this issue. I understand the requirements and can deliver a solution that meets the expected outcome.

I'd love to work on this. I understand the requirements and can handle the implementation.

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

[retkatmun]

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

Hi Maintainer,

I’m a smart contract and full-stack developer and would love to contribute to this issue. I’m an experienced contributor with hands-on expertise in Rust, Soroban, Cairo, and TypeScript.

I’m passionate about building secure, scalable blockchain solutions, with a strong emphasis on writing clean and maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 24 hours of assignment.

I’d greatly appreciate the opportunity to contribute and help move this forward.

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