[SC-51] Cross-contract integration tests

[yusuftomilola]

Overview

Tests today are per-crate and exercise contracts in isolation. Real flows span crates — a high-value asset transfer touches the registry, multisig approval rules, and the audit trail — and the seams between them are untested.

Tasks

• Add an integration test target registering multiple contracts in a single test Env.
• Cover: register asset → initiate high-value transfer → multisig approval threshold reached → ownership updated → audit entry written.
• Cover the failure path: threshold not reached leaves ownership unchanged with no partial state.
• Cover an unauthorized actor being rejected at the approval boundary.
• Cover a maintenance record written against a registered asset.
• Assert the event sequence across contracts, not just final state.
• Document the setup so new integration cases are easy to add.

Acceptance Criteria

• At least three multi-contract flows are covered end to end.
• A mid-flow failure leaves no partial state in any contract.
• Integration tests run under cargo test --all in CI.

Dependencies

Best after [SC-32], [SC-40], [SC-45].

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

[temitope-007]

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

Hi maintainer

I'd like to take up this issue

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

[Emoji-dot]

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

I would like to work on this issue

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

[chi797]

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

I’m a smart contract and full-stack developer who turns complex ideas into secure, production-ready blockchain code.
With strong skills in Rust and Solidity, I build systems that are fast, safe, and built to last.
My experience with the Stellar SDK lets me ship real-world Web3 solutions that actually move value

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

[TomikeDS]

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

can i work on this issue?

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

[drips-wave]

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

🧑‍💻 @TomikeDS: 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 🌊