[SC-41] Expand asset-maintenance test coverage (729 lines, only 4 tests)

[yusuftomilola]

Overview

contracts/asset-maintenance/ is 729 lines across just lib.rs and test.rs with 4 #[test] functions. It records maintenance history on-chain, which is audit evidence — incorrect or forgeable records undermine the point.

Tasks

• Enumerate every entrypoint and add happy-path plus failure-path tests for each.
• Test maintenance record creation, update, and completion, including invalid status transitions.
• Test authorization: only permitted roles may record or amend maintenance; add negative tests without mock_all_auths.
• Test that historical records cannot be silently altered or deleted — this is the core audit property.
• Test date and scheduling boundaries, including records scheduled in the past.
• Assert every error variant is reachable.
• Consider splitting lib.rs if it carries several distinct concerns.

Acceptance Criteria

• At least 25 tests covering every entrypoint.
• A test proves historical records are immutable through the API.
• Authorization boundaries are covered by negative tests.

Notes for Contributors

Requires Rust + Soroban. Workspace: contracts/ (soroban-sdk 22, 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.

[georgeonweb3]

Hello, I'd appreciate it if this issue was assigned to me, I'm confident I should be able to finish and submit a PR within a day

[Fash004]

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

Please assign this issue to me

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

[tolulopedd26]

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

can i handle this?

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

[drips-wave]

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

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

@tolulopedd26's PR #1228 was approved and merged by @yusuftomilola.

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

👏 Great work, @tolulopedd26! Keep contributing to DistinctCodes.

[drips-wave]

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

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