Yeah, I looked but it’s really hard to detangle in a way that retrospectively leads to two sensible conversations. It’s somewhat natural that a discussion proposing a specific curation rule would end up discussing the pros/cons of more curation more generally and potential alternatives.
For me, personally, the most valuable “curation” to have wouldn’t be about code quality or docs or utility or provenance at all. It’s about the fact that it’s open source with an invitation for collaboration. And even more importantly, with someone continuing to maintain the package post-registration. All of the other things are signals in favor of a well-stewarded package, but it’s the stewarding itself that’s most valuable — and most costly!
In other words, the trouble I have with a vibe-coded package is that it’s (to me) a fairly strong signal that the stewarding is already weak to the point of being problematic. That’s not necessarily true, but it’s a signal.