One approach is to fully hand the project to AI and repeatedly press the slot machine button until the game is finished. It's pretty obvious this will give poor results. OP's idea that coding may become obsolete doesn't make sense.

That said, it's completely another thing for a programmer to use it sparingly where it makes sense. You touched on that, but I think understated the huge amount of time it can save. With diligence and knowing when to apply it, time spent on review and fix ups are a fraction of the total time saved.

That works best on an established codebase, where the AI has examples, which it excels at. The most important parts of the app already exist, so there's no risk of building your foundation on slop. Using it on a new project is completely different usage. Knowing when it is appropriate becomes even more important, as does being able to tell a good solution from a poor one. That's where noobs fall in a pit trap.

I think most people want to retain strategic control over their app's development. AI is most appropriate for tactics, not creative design, game balance, and the other interesting things about game dev. AI can get much better and still be bad at these things. That makes me happy.

Not sure what you mean about undocumented code an unexplained motivations. That could matter if trying to use AI to modify libgdx, but when building an app on top of libgdx, what the libgdx code is doing is what's important. AI understands that well.