[SC-81] CI's wasm-size-delta baseline should be re-verified once contrib's compiled surface changes

[yusuftomilola]

Overview

.github/workflows/CI.yaml's wasm-size-delta job compares contracts/scripts/check-wasm-size.sh output between base and head using contracts/scripts/wasm-size-baseline.txt — once [SC-57] either compiles seven previously-dead contrib files or deletes them, contrib's WASM size will legitimately jump or shrink by a real, one-time amount that isn't a regression, and the baseline should be regenerated deliberately alongside that change rather than surprising whoever's PR happens to land it with an unexplained size-delta failure.

Tasks

• When [SC-57] lands, regenerate wasm-size-baseline.txt for contrib as part of the same PR, with a note in the PR description explaining the expected, intentional size change.
• Confirm check-wasm-size.sh correctly attributes the size change specifically to contrib and doesn't mask it against the other four crates' totals.

Acceptance Criteria

• The WASM size baseline is updated deliberately alongside [SC-57], with a documented reason, rather than as a surprise CI failure on an unrelated later PR.

Dependencies

Must land together with [SC-57].

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.

[Tosme005]

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

Hello, I reviewed the issue requirements and have tackled similar implementations in the past. I’d love to take ownership of this to deliver a clean, well-tested solution. Please consider assigning it to me

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

[onakijames-droid]

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

Hi maintainer... I'll work on this issue and submit a PR for it ASAP

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

[69starman]

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

Hello sir maintainer....
I have a vast experience in solving github issues ...
Please do well to assign me this let me get it done for you ✅.
Thank you 😊

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

[Imole2001]

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

Hello, I've carefully reviewed the issue description and have a solid understanding of the expected outcome. I'd be happy to work on this issue and deliver a solution that meets the project's requirements.

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

[AKAEMM668]

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

I have carefully reviewed the requirements and understand what is expected. I am confident that I am capable of handling this task and delivering a high-quality solution that meets all the necessary criteria. I would appreciate the opportunity to demonstrate my ability through the work.

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

[hauwauyahass-byte]

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

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @hauwauyahass-byte 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.

[doncross03]

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

Hello Maintainer, I have carefully reviewed this issue and understand the requirements. I am confident in my ability to implement a solution that meets the expected outcome. Kindly assign it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @doncross03 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.

[drQedwards]

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

Reverify work handled. But only if you assign within the hour.

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

[Dhivine-stack]

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

Hi Maintainer, I've gone through the issue and have a clear understanding of both the problem and expected outcome. I can implement a focused solution that fits the existing codebase and would be happy to take this on.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Dhivine-stack 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.