.github/workflows/ci.yml's wasm-build job builds all three contracts to .wasm and then does nothing further with them — no actions/upload-artifact step. This means nobody can download a CI-built .wasm from a given commit/PR to sanity-check it against a locally-built one, or diff two commits' compiled output byte-for-byte, without rebuilding locally from that exact commit. Given how much this repo already documents caring about build reproducibility (the already-open #59, the various TTL/determinism-focused issues), surfacing the actual build artifact from CI runs would make manual reproducibility spot-checks much easier — currently the only artifact of a CI run is the pass/fail signal.
.github/workflows/ci.yml'swasm-buildjob builds all three contracts to.wasmand then does nothing further with them — noactions/upload-artifactstep. This means nobody can download a CI-built.wasmfrom a given commit/PR to sanity-check it against a locally-built one, or diff two commits' compiled output byte-for-byte, without rebuilding locally from that exact commit. Given how much this repo already documents caring about build reproducibility (the already-open #59, the various TTL/determinism-focused issues), surfacing the actual build artifact from CI runs would make manual reproducibility spot-checks much easier — currently the only artifact of a CI run is the pass/fail signal.