Stuff like this is what gives CoCs a bad rep, although when implemented well, they can be hugely beneficial to communities.
A key part of "implemented well" is the interpretation and execution by whoever is in charge. Unfortunately, there isn't really a way to know, or ensure, that a group of people will act in good faith and accordance with a document that they say they adhere to. That seems to have been part of the problem here -- Mr. Howard notes several ways in which the committee acted against their own code. I think this is (part of…
I do agree Codes of Conduct are a tool like any other, but it's a tool that I've personally seen being misused so many times, it admittedly starts raising red flags. And if there's something human beings excel at, it's in finding patterns, no matter if they're poorly justified or not.
Subconsciously, I'm already avoiding contributing directly to projects with strict CoCs, and it's a bit painful when I do realize it, even if I've never willingly (or unwillingly, by virtue of keeping most communication with maintainers short, polite, straight to the point and erring on the side of caution) broken any.