You can say, "go off and fork the project", and you'll get 20 forks, each one person's pet PR applied, and no more future progress without a dedicated maintainer triaging and coordinating all this stuff in one place. You are asking projects that are surviving but not necessarily thriving to simply die. And for what? To satisfy downstream developer demand for their AI-generated contributions to be accepted?
Not all contributions are equally valuable, and that is notwithstanding AI use. AI facilitates volume but not necessarily quality. Why should anyone spend resources benchmarking and reproducing a non-issue, or a PR that will not otherwise pass muster? We can automate a lot, but human judgment is still critical in making things to be used by humans.
how does the presence of those forks contribute to the project's demise in any way?
Of course. So do you want a Grand Vizier to ban forks that are not valid so software runs the way it should be run?
>you'll get 20 forks, each one person's pet PR applied
Sure; if the primary repo goes unmaintained, and nobody else steps up to maintain a fork, yes you might get multiple forks that solve a specific users individual issue. I'm not sure there's a way around that.
The comment I was replying to sounded like someone who was unavailable to handle non-AI requests as well. AI contributions is making it worse, though my biggest projects haven't been hit by it yet <knock on wood>.
Low quality contributions is a very real problem, I agree with that.