I thought we said somewhere that this was a power tool to be used very carefully, by an expert who understands it?
If it is made more accessible to non-experts doesn't this mean that we risk people critically breaking their database through some bug in our logic, beyond their ability to resolve it - all just so the schema can be 100% perfect (the user probably would never have known it wasn't TBH).

There's also the consideration that some of these fixup queries could take minutes to run on large sites, and time out, causing serious confusion, and potentially bringing down a site if the user keeps hitting refresh.

What is the driver for running commands direct from the UI?

Yes it does say that. You have good points there.

I'm not sure what your question is asking. Commandr is coming to mind but that's probably not what you meant.

I just mean, why is this being considered? Is what we're doing confusing someone, putting something beyond their skills, or maybe something you just saw as unnecessarily laborious?

The latter... unnecessarily laborious as it would require manually going into the database and running the queries.

However, perhaps that is ideal as it necessitates more time to think about what you're doing. However, if we keep the current behaviour, I would recommend changing the action text "Correct MySQL Schema Issues" as it doesn't actually correct them. Perhaps, "Check for MySQL Schema Issues".

Sounds fair to me.

I changed the language as indicated in the comments but the core issue itself won't be done.