How to avoid API compatibility issues when launching new features in legacy projects

I recently ran into a specific problem while adding an approval workflow to a legacy React + Node backend: after the new fields were deployed, the old version of the mobile app read the order status as empty, leading customer service to believe the approval requests were lost. On the surface, it looked like a single point of failure, but it actually involved processes, systems, and on-site…