refactor: split cross-kind y-tag changes into scoped follow-up PRs for safer review

[mostronatorcoder]

Context

#653 changed y tags across multiple event domains (orders/info/dispute/admin/dev-fee) in one PR.

Problem

Large cross-kind protocol changes are harder to review and reason about for compatibility impact.

Requested follow-up

• Define a PR-scope guideline for protocol/tag changes:
  • single-kind PRs preferred, or
  • explicit "cross-kind protocol change" checklist in PR description
• Add reviewer checklist item for external contract impact (indexers/clients)
• Add "scope declaration" section template in PR body for protocol changes

Acceptance criteria

• Contributor docs (or AGENTS.md) include scope guidance
• Future protocol-tag PRs include explicit scope + compatibility statement

Related

• Lessons learned from Adding instance name to "y" tags #653

[codaMW]

Hello team, has this issue been taken up?

[JiwaniZakir]

Working on it.

[codaMW]

Thank you so much @JiwaniZakir !, glad to know that you are working on it. All the best

[JiwaniZakir]

The scope guideline and checklist additions make sense — cross-kind protocol changes touching orders/info/dispute/admin/dev-fee simultaneously make it hard to reason about compatibility impact per domain. Adding a "scope declaration" section to the PR template with an explicit compatibility statement (what indexers/clients need to update) would catch this early. Happy to draft the AGENTS.md section or PR template snippet if that helps move this forward.