(Not a duplicate of Preventing bad edits from unlocking votes, as that covers users editing posts to unlock their own vote; this is about automated scripts editing posts.)
This may seem like a minor bug, and I thought so too for a long time, but I'm reporting this now because the supposed scenario I thought of at the time actually came to fruition recently. (This isn't a duplicate of that either, since that's a question asking about the scenario and why it happens; the answer points to the fact that automated script edits were made. This is a follow-up request from that answer.)
Votes are locked after a 5-minute grace period. Any edit made after that period unlocks the vote permanently. This is no matter what edit was performed (major and substantive, or really minor), and no matter whether the edit was done by a human or by an automated script written by SE.
In the above case, a user had many of their posts unupvoted as a result of the script that edited HTTP links to HTTPS a while back. Not too far while back, we had a user suspended as a result of massively unaccepting answers; such massive vote retraction would be prevented by this.
Note that we already have a special case for such edits: they are explicitly prevented from bumping posts, while other forms of Community user editing (e.g. anonymous edits) do bump posts. Can we piggyback on this to make it so that the Community user's automated script edits don't unlock votes?