fix: scope fee profiles to their measured chain

[MuncleUscles]

Summary

• require exact chainId provenance before applying developer fee suggestions
• safely fall back for unscoped, malformed, wrong-chain, or below-floor profiles
• re-estimate unsafe profiles through SDK network defaults so distribution and fee value remain coherent
• clarify the boundary of live policy verification

Root cause

Profile selection used only deploy/method name. The human-readable network label was not a security boundary, so allocations measured for one chain could be reused on another while live price-cap verification still passed.

Validation

• core: 21 tests
• React: 16 tests
• Vue: 13 tests
• release policy: 6 tests
• full typecheck and build
• 3 package tarballs validated

Downstream

The testing-suite profile generator must emit numeric chainId. Legacy profiles deliberately fall back to network defaults, and the Boilerplate RC no longer loads its stale profile.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 2b5d30ae-b117-4707-a39b-ffaf4f677fd2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}