My team has also adopted this - it's much easier to add another layer than to refine or simplify what exists. We have AI skills to help us debug microservices that call microservices that have circular dependencies.
This was possible before but someone would maybe notice the insane spaghetti. Now it's just "we'll fix it with another layer of noodles".
Unfortunately I saw this pre-AI with microservices, where while empowering developers with their beloved microservices, we create intense complexity and deployment headaches. AI will fix the slop with an obscuring layer of complexity on top.
Are you concerned this will just lead to coupling everywhere like microservices tend to do?
That's so interesting because where I work, the push was to "add one more API" to existing services, turning them into near monoliths for the sake of deployment and access. Still a mess of util and helper functions recursively calling each other, but at least it's one binary in one container.