[SC-80] asset-maintenance's aggregate calculation functions need edge-case tests for empty/zero input

[yusuftomilola]

Overview

calculate_total_maintenance_cost, calculate_asset_downtime, and get_asset_health_score (contracts/asset-maintenance/src/lib.rs) are exactly the kind of aggregate/derived-value functions where the empty-input case (an asset with zero maintenance records) is easy to get wrong (divide-by-zero in a health-score average, an unhandled empty-vec fold) — worth dedicated tests for a brand-new asset with no history at all, distinct from the general edge cases in [SC-66]/[SC-67]/[SC-68].

Tasks

• Add a test calling all three functions against an asset id with zero maintenance records and assert each returns a sane default (0 cost, 0 downtime, a defined health score) rather than trapping.
• Add a test with exactly one record, to catch off-by-one issues distinct from the zero and many-record cases.

Acceptance Criteria

• All three aggregate functions have explicit zero-record and single-record test cases.

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.

[cyberdocs120]

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

I’d like to work on this issue because it addresses an important area of the project and presents a great opportunity to make a meaningful contribution. I’m particularly interested in delivering a solution that is reliable, maintainable, and aligned with the project’s existing architecture and development standards.

I have experience working across software development, including backend and frontend development, APIs, databases, testing, DevOps, and blockchain-based applications. I’m comfortable understanding existing codebases, identifying the root cause of issues, implementing clean and scalable solutions, and writing thorough tests to prevent regressions.

My approach would be to first understand the existing implementation and project conventions, then develop the solution in a focused and incremental way. I’ll ensure the changes are well-tested, documented where necessary, and do not introduce unnecessary complexity or break existing functionality. I’m also committed to clear communication, responding to review feedback, and delivering a polished contribution that provides real value to the project.

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

[Johnjnr1]

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

Hi, I'd like to work on this issue! because I am very conversant with solving problems like this!

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

[NeduTheDev1]

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

Please assign to me maintainer I can handle with ease

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

[Fashola-Oba]

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

Hello, I’m interested in contributing to this issue. After looking through the requirements, I believe this is something I can work on effectively. I’ll take some time to understand the current implementation and project conventions before making the necessary changes. I’ll also include appropriate testing with the contribution.

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

[Tekh134]

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

Hey maintainer! Good to be back
I’ve contributed here before with merged PRs.
Can I take up issue ? please assign me. thank you .

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

[akansmafengadamu]

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

Hello maintainer
I would love to contribute to this Issue and I assure you the best result which matches your expectation

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