This is expected behavior, not a bug. The guard you are hitting is intentional — it protects against a class of mistakes that used to cause data loss.

If you need the other behavior, there is a documented filter you can hook to override it per site.

Appreciate the clear steps. The dry-run tip in particular saved me from a mistake I would not have caught otherwise.