This reasoning assumes any LLM-assisted change is faulty, right?

The linked article doesn't make me concerned. They seem to have the expertise, seem to apply due diligence and good practice around (selectively) using LLM.

Can people not directly involved in and working on the project assess the risks well? Do we not have to depend on author and project leadership expertise just like we had to before with any parts of development, management, and tool and infrastructure use?

I haven't looked up the original communication or drama, but I assume communication could have been much better. Maybe the commits didn't say much about the reasoning and due diligence that they describe in this article? Other than that, how can you make a better judgment about the changes than them without taking a thorough look and assessment?

Point it out, doesn't change the fact that you're not addressing the core problem, which is developer burnout in these FOSS projects.

Also no its not their work, its literally a voluntary job so stop dictating how people spend their free time.

But that's just me, you do you.