I'm a huge AI advocate but even I can't get on board with this.

Feel free to fork the kernel and maintain your own vibe-coded disaster.

I'm confused by your answer, the previous post doesn't seem to be about vibe-coding at all.

It seems to be more about:

1. auto grouping duplicate security reports

2. auto validating if they are likely viable or likely nonsense

3. auto checking if they have recently been patched

4. auto assessing if they likely "invalide" for other reasons (e.g. they are for a very old long time no longer maintained Linux version, out of tree drivers, etc.)

I mean practically all of that isn't trivial to get working in a way appropriate for the Linux security mailing list and comes with many not so obvious complications. But also non of that is vibe coding and in most cases this is is more about AI doing a per-assemsment of send security issues to speed up the review of them, then it is about the AI doing the final decision.