I think the article is over complicating things. I work in a project which is heavily forked for a variety of reasons. While it’s academically interesting to look at the reasons for those downstream forks we have no interest in going to the considerable effort of tracking them all.

If you can take a project and use an LLM to enable your niche use case then more power to you. FLOSS was never about ensuring all patches flow upstream.

I honestly prefer if those that have Claude fix their forks keep said forks private and go on with their lives.
They overwhelm the main with their commits and forces the developer to wade through their AI slop that they couldn’t care less to check for quality and security themselves. Then they get angry that their commits aren’t accepted as the fix.