How should backward-compatible API changes be designed for production?

For production, prefer additive changes, preserve defaults, tolerate old request shapes during migration, use contract tests, and verify real consumer behavior before removing compatibility code. 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.