Three weeks ago, the Cortex 2026 Engineering in the Age of AI Benchmark put incidents per pull request up 23.5% and change failure rates up roughly 30% since AI adoption accelerated. I wrote about that data and what it means for blast radius shortly after it landed. What I underestimated at the time was how fast the language was going to shift. The phrase that's settled into the conversation since isn't "blast radius" or "service catalog." It's cross-repo context . And it's almost always being used in the same sentence as "AI coding agents." The reason becomes obvious once you read what teams operating AI coding agents at scale are publishing right now. They're not writing about AI making them faster. They're writing about the infrastructure they had to build so AI could ship safely across more than one repo at a time. Three teams have published, in the last six weeks, the same diagnosis with three different solutions.…