> My understanding is that she did a PR, quickly merged it, and people only noticed after it had already happened. Nobody interjected to complain; there wasn't really time to do so.
The PR is here, it was explicitly rejected (with two comments) and closed before she merged it
Perhaps because nobody has asked her to do so. Despite the contribution process not being followed, the results are seemingly desirable; and so nobody seems to want to worsen the codebase by reverting the change, even temporarily.
Process is great when it improves quality, but process followed just to follow process—when it won't result in a change in quality—is just pageantry. Engineers are generally too practical (and impatient!) to participate in pageantry, even as an act of public humiliation for someone they're annoyed with.
The repo has other maintainers; any of them could have reverted the merge and demanded the PR process be followed, if they thought it was a good idea to do that. What intent do you derive from their inaction?