This shouldn't actually change virtually anything. We had this happen recently, and were able to rollback within minutes. Devs hand-coding stuff breaks things too. If you already have good observability, fast rollback processes, and feature flag new changes plus do % based rollouts to limit the blast-radius, then it's more or less the same.

sounds like bad deployment practices - canaries, guardrails, fast rollbacks, ring based promotions, cell based architecture, blah blah etc... humans write bad code too, there should be systems in place to protect it from releasing

"Ah I see your org hasnt yet had an outage caused by a bad LLM code push"

"We went back to shovelling by hand because someone ran over the pole with the front-loader, even though he had no experience driving it."

This is definitely user error; obviously it's a hard tool to wrangle but it's entirely possible to use it safely.