[GrantFox][Medium] Add WASM and per-entrypoint regression budgets

Summary

Add WASM and per-entrypoint regression budgets

Why this matters

Contract size and gas regressions can block deployment after unrelated changes.

Scope

Track deterministic budgets for settlement, oracle, pause, and query paths.

Acceptance criteria

• Baselines and tolerances are committed.
• CI reports exact size/gas deltas.
• Intentional updates require reviewed baseline changes.
• The checks run on clean builds.

Validation

Add regression coverage for existing behavior, failure modes, authorization boundaries, and compatibility. The implementation must pass the repository CI checks.

Non-goals

• Typo-only, formatting-only, or documentation-only changes.
• Unrelated refactors or dependency upgrades.
• Weakening existing security, authorization, CI, or production safeguards.

Contributor application

Before implementation, comment with relevant experience, a 1–4 bullet approach, and an estimate for opening the first draft PR. Wait for maintainer assignment before coding.

PR requirements

Use a feature branch, include Closes #<issue-number>, check every acceptance criterion, link criteria to code/tests, explain security and failure-mode considerations, and pass CI.

Reward-readiness

This is a substantive GrantFox campaign issue. Merge and CI success do not by themselves guarantee reward eligibility; final reward-readiness is determined by campaign review.

Start by reviewing the repository CI and the settlement, oracle, pause, and query entrypoints mentioned in the issue, then identify how clean builds expose WASM size and gas measurements. Done means committed baselines and tolerances, exact CI deltas, reviewed baseline updates for intentional changes, and regression coverage that passes repository CI.