fix: add missing check for sequence numbers in commit report offramp

[vicentevieytes]

No description provided.

[github-actions]

👋 vicentevieytes, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

[Copilot]

Pull request overview

This PR adds validation to prevent invalid sequence number intervals in commit reports. The title indicates a fix for missing checks on sequence numbers in the offramp commit report.

• Adds validation to ensure minSeqNr matches the source chain config and minSeqNr <= maxSeqNr
• Implements previously stubbed load methods for deserializing commit report data structures
• Adds comprehensive test coverage for the new validation rules

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
pkg/ccip/bindings/offramp/offramp.go	Adds ErrorInvalidInterval error constant
contracts/wrappers/ccip/OffRamp.ts	Adds InvalidInterval error enum value and implements load methods for RampMessageHeader, Any2TVMRampMessage, ExecutionReport, and execute message
contracts/tests/ccip/OffRamp.spec.ts	Adds two test cases validating the new sequence number interval checks
contracts/contracts/ccip/offramp/errors.tolk	Adds InvalidInterval error to the error enum
contracts/contracts/ccip/offramp/contract.tolk	Adds assertion to validate sequence number intervals in commit reports

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[patricios-space]

Should we bundle this fix with the ones we are merging in PR #430?

[vicentevieytes]

@patricios-space

Should we bundle this fix with the ones we are merging in #430?

If you think that's better we can do that. I don't think it's necessary.

[patricios-space]

Awesome