

I’m not against any of that.
What I disagree with is that this is a priority. It’s a nice-to-have.
Once mod actions are supported, and an API exists, any imaginable automation can be implemented by anyone with the impetus to do so.
As such, the priority of further integration drops drastically and platform developer attention can and should move elsewhere.
Mod tools are best created by the people who use them. Even better when they are created for the needs of a specific community. As such, more advanced features should be deferred until later.
Once communities grow large enough that there are a significant number of moderator-developers around, it might be worth creating a generic bot that can be configured as needed. (As has happened with reddit, discord, etc.)
Asking for these tools before then, is inefficient, because the people who ideally should be working on them, haven’t shown up yet, and the platform developers time is better spent on other things.
That’s not what I’m saying.
Obviously not everyone needs to code. Once I write a bot, it could potentially be used by anyone.
Only a small percentage of mods need to also be developers. But since that group isn’t big enough yet, the solution is growth.
Not asking the platform devs to do even more. They too, are volunteers.