I think for a lot of people it's that they stopped caring or obsessing over the (perceived) small details; AI makes it very easy to work on a higher level. I suspect (don't quote me on this) that it's the same for a lot of developers that grew to more lead / managerial positions - at some point the details don't matter much to you personally and you need to spend your energy elsewhere.
But I hope people are gathering metrics. We had an extra meeting the other day because we're seeing an upwards trend in outages, the meeting was mainly about how it affects various departments (like customer support) and potential revenue loss (can't sell a product/service if the signup page is down for three days).
Thing is, there's no one cause for any of those - we have hundreds of engineers, dozens of applications and 3rd party integrations, millions of (potential) customers each running their own set of devices, and it's pretty much impossible to control everything.
But this goes beyond whether or not code was written by an attentive hand working under a strict set of policies or an AI that figures it out on the go, and goes up a level to things like realtime monitoring and incident responses.
You're right that as a person moves into management/staff+ that individual details matter less for them, because they begin to deal at a more strategic or operational level, but someone still needs to obsess over the small details (to make things easier, let's assume we're only talking about the details that actually matter and that there's broad agreement what that set is). It's not that those details stop mattering to them, it's that they have to depend on the assumption/promise that someone else is going to mind those details for them, so that they can work on things with a broader perspective.
The problem comes when no one is actually minding those details anymore. If those details aren't actually minded, then the work at the higher levels will be much less useful and effective, and in the worst cases won't matter at all.