There's a more general problem. We need to figure out how to use LLMs and still have decent code quality.
One possibility is to have firmer APIs for known components. APIs that come with the entry and exit conditions for proof of correctness. That gives an LLM a hard definition it can work to meet.
This isn't as bad as it used to be. We may be able to use LLMs to create entry and exit conditions from specs written for humans and from unit tests. Code is cheaper than it used to be, but so is formalism.
This may be a way to put firewalls around AI slop.
It's your code review process (with or without agents). If you don't hold this fort, the battle is lost, and the repo is going to devolve.