You don't. This is the kind of problem created by vibe coding. Escalate upwards, challenge the policy, cite this as an example. Also cite things like https://a

You don't. This is the kind of problem created by vibe coding. Escalate upwards, challenge the policy, cite this as an example. Also cite things like https://arxiv.org/abs/2511.04427 https://arxiv.org/abs/2511.04427 : "transient increase in project-level development velocity, along with a substantial and persistent increase in static analysis warnings and code complexity". If the policy doesn't change, find a new company. Now, all that said: it would also be a good idea to have better testing infrastructure that actually tests the services in concert and not just individually. That testing infrastructure will be useful for the humans who take over from the vibe coding and start cleaning up the mess.