contract-first-change

name	contract-first-change
description	Use when a feature or flow change adds fields, changes packets, changes reports, or affects routes, wrappers, policies, or APIs.

1. Identify the contract or contracts that own the change.
2. Update the contract docs and validation notes first.
3. Update examples immediately after the contract.
4. Only then update implementation notes or code scaffolding.
5. Check for backward-compatibility and migration risks.