I think it is mastake to lay this completely at the feet of ICs. What you are describing is a form of engineering, and a lot of management feels that "engineering is solved" (not just "coding") and have no patience for these things. ICs are being forced into extremely naive and unsophisticated AI usage by managers with incorrect mental models. That's why so many ICs are cranky.
Its out there, it can do things, and it has its limitations. What it can do gets lot of light, and what it can't do well becomes a ICs 'skill issue'. Say with AI your velocity can go up by factor or X, but expectation is Y where Y >> X. This leads to lot AI-usage which is nothing close to "engineering". The whole idea that engineer should be able to defend what they build, while showing productivity gains that are factor Y can't be done without cutting corners, and it looks like leadership is mostly ok with it as long as it not immediately causing problems.
This is again not problem with AI essentially, but the overly optimistic expectations from it.
No, and it's the same with leads, they can be given a system they understand but need to reference it.
I'm very certain these are people brushing up against their lack of processes, workflows, or engineering practices.
The context are large enough. You do not need to understand the world to build a chair.
I see the very opposite in many different domains happening now, and some codebases are monsterous. They are figuring out ways that do indeed work well.
The engineers that are figuring out these problems when working with a new tool, will have jobs.
Those who continue to doubt, and distance themselves are the ones that will be behind.