[tstrimple]

This is no different than making changes in any micro-services environment. You have to be careful. You've got existing contracts with other services and typically you don't just change things like that. If your environment is large enough to actually need micro-services, that means the lines of communication between the owner of the service and the consumers of the service have exploded to the point any change is basically impossible. So when you "rename" a field. You add a new field and maintain the old one to allow consumers of your service to transition (prompted by deprecated warnings) gracefully. You monitor when your old value is no longer referenced and then you remove it.

It's also telling that none of your tests caught the issue. Why don't you have consumer like tests of your services? If after every change, you're testing your micro-service against what your consumers are actually sending you failures like this show up quite easily. This isn't a failure of vibe coding. This is a failure of properly architecting and testing your micro-services. It happens all the time when companies just try to blindly follow what Netflix engineers are doing without understanding the nuance and tradeoffs.