>they do mistakes like this sometimes.

So do I, which is why I don't open the terminal to production database.

>anything below SOTA + higher reasoning efforts seems to fall into these mistakes sometimes.

We figured out how to deal with the human version of this mistake -- add a robust layer with build-in checks between the sloppy meatsack and production data and also make it annoying to access, so it does not become a habit and also requires high reasoning effort.

In my developer environment I can afford this mistake and can afford to delete everything I can touch. For some pieces the recovery will require more effort, but ultimately I can also have my laptop stolen on the way from the office.

On production however it will be a stack of forms to fill, a script with the dry-run and a four-eye rule to approve running it. We will also be able to recover production from the backup as we should. Or at least the company collectively believes so.