<...>
Well the bug is no longer an issue, and has run the full software development cycle in a short amount of time: reported, measure of impact, resolved and rolled-out, tested, twitched and rolled-out, re-tested, verified and settled.
Note: I looked through the list of cases I compiled with the 317 TXs (out of which half were likely due to the double/triple click ex-bug effect), and found no obvious case of the scenario you hypothesize (all lower ranked cases involved as Senders had enough sMerits to cover the double send at the time, and higher-ranked are more likely due to airdropped sMerit).
<…>
I wouldn’t really call it a user negligence … anyway, it was a minor incident that has been fixed or software-shaped to be avoided.