Took me a while to figure out what you were talking about; that edit was almost a month ago.  The explanation on the page suggested that making the edit would block the script running the bot from its source, which was the intention.  Blocking the IP it was using as a logged-out bot, which is what was originally done, was causing collateral damage.  All bots are supposed to know that they're logged out and stop themselves (or be able to log themselves back in); the absence of that section of code is a serious matter, because bot editing is restricted to named bot accounts, and is essentially a malfunction.  Just think if someone had blocked the range (which someone was considering doing!), not realizing that it was the WMF Labs - none of the Labs-based tools regularly used on this project would have functioned, and cross-wiki bot activity would also have been adversely affected.  Better than 90% of bots include code that tells the bot how to check if it is logged in, and what to do if it is not, and many that don't require hands-on control. There's no reason for these ones not to include that code. Heck, they can probably swipe it from one of the other open-source coded bots currently in operation.  
I'm also confused by your statement,  was the bot blocked or not? and was it editing logged-in or logged-out? If it was editing logged out, then there's an even more serious problem because it should always need a manual restart after a block.  If it was editing logged-in, then the "kill switch" isn't working.  So, no matter how you look at it, something's not working right.