How should GraphQL schema evolution be designed for production?

For production, favor additive changes, mark fields deprecated with migration guidance, measure field usage, keep old behavior during a transition window, and remove fields only after consumers migrate. Add automated tests and observability around the critical behavior, document ownership and failure handling, and review the design when traffic, dependencies, or security requirements change.