I don't believe there's a *cough* canonical list of issues, though there are various nooks and crannies where discussions have taken place. These can serve as a kind of record for various things that have come up. And, as happened in this case, the monastic record also help.)
Traditionally, it's been up to the volunteer teams (like pmdev, janitors, etc.) to handle various clean-ups and repairs. (The implied expectation, of course, being that these volunteers would keep an active watch for such things and use their discretion to handle things quickly, efficiently, and with a minimum of fuss.)
(Aside: In some corporate environments, this is called "a bias for action.")
<Update> (to respond to AM's reply):
It's not entirely a mental todo, but rather a different way of looking at things. Not everything needs a heavy process of triage, review, and approval. Some things can be handled from a more pragmatic "see something that needs to be done, do it, and carry on with your day".
If you'll forgive a bit of linguistic playfulness in this instance: veni, vidi, refeci...
What do you care? You just want to see PerlMonks die already. Are you fishing for more reasons to justify your hateful opinion?
The answer happens to be yes, the pmdev group have a "to do" wiki where they log both bugs and enhancement requests, not including those which are knocked off more or less as soon as they are identified.
I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.