You are reviewing a PR that renames a response field used by frontend and external clients. What do you check before approving it?

Before approval I require a rollout and removal plan, not just a code change. CI compares the published contract, compiles representative generated clients, and runs consumer scenarios against the provider. The release adds privacy-safe telemetry for use of the old version or contract path where that can be observed reliably; absence of a field in server logs alone is not proof that no client reads it. Communication identifies owners, migration examples, dates, and support escalation. During rolling deployment both server versions and shared data remain compatible, and rollback does not emit a shape neither client understands. If dual fields create ambiguity or security risk, a clean new version is preferable. Removal occurs only after the support window and consumer evidence are satisfied, with contract snapshots and release notes updated in the same change. That turns a subjective naming cleanup into a controlled compatibility decision.