Read this article on Signadot .

Most merge gates stop at build, unit tests and contracts. Coding agents clear those easily, so the check that matters most, behavior against the real system, has to run before merge.

Pick a merged pull request with a green check and ask the team what the check guarantees. You will hear which jobs ran. You will rarely hear what anyone downstream can now assume.

That matters because main is shared ground. Other teams cut branches from it, ship their own services against it and, when something breaks, start from the belief that what was already merged is correct. Every merge makes that promise to them, usually without anyone stating its terms.

Leaving the terms vague was cheap while people wrote each change and stuck around to support it. Coding agents undo both. They raise the number of PRs, and a growing share comes from sessions that keep no memory once the work is handed off.…