ci.yml's WASM build/upload step references an unrelated project's contracts

[martinzhames]

Category: ci

Problem

.github/workflows/ci.yml's final two steps are:

- name: wasm build
  run: cargo wasm-build
- name: Upload WASM artifacts
  uses: actions/upload-artifact@v4
  with:
    name: wasm-contracts
    path: |
      contracts/paylink/target/wasm32v1-none/release/paylink.wasm
      contracts/cheese_pay/target/wasm32v1-none/release/cheese_pay.wasm

cargo wasm-build is not a real subcommand available in this workspace (no cargo-wasm-build alias is defined anywhere in .cargo/config.toml or Cargo.toml), and neither contracts/paylink nor contracts/cheese_pay exist among the 14 real member contracts under dabdub_contracts/contracts/. The Codecov step just above it is also still named name: cheese-contracts. This is leftover boilerplate from a different project template that was never adapted when this repo's actual contracts (payment_escrow, merchant_registry, etc.) were added.

Impact

CI's WASM build/upload step silently does not build or validate WASM output for any of this workspace's real 14 contracts — it either fails outright (since the referenced paths don't exist) or, if cargo wasm-build happens to resolve to something unintended, produces artifacts nobody can use. Critically, ci.yml never invokes make check-wasm-size, so the documented 64KB WASM size budget (Makefile, WASM_SIZE_LIMIT := 65536) is enforced only in deploy.yml, on the push: main/tag path — a pull request that grows a contract's WASM past the 64KB Soroban deploy limit would not be caught until (or unless) it merges.

Suggested fix

Replace the stale steps with cargo build --target wasm32v1-none --release across the real workspace and make check-wasm-size, uploading the actual per-contract .wasm files under dabdub_contracts/target/wasm32v1-none/release/*.wasm, so pull requests get the same 64KB budget gate that deploy.yml already enforces on main.

[Marvy54]

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

Hi! I’ve reviewed the issue and understand the requirements. I’m familiar with this stack and can start immediately. Please assign this to me. Thank you!

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

[echoripplestudio]

@echoripplestudio 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 @echoripplestudio to this issue.

[drips-wave]

Congratulations, @echoripplestudio! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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