And I think that *horribly* muddies the definition because programming and getting a bit of AI help here and there (since it's read the docs better than you have, and scanned Stack Overflow for common problems and mistakes more thoroughly than you have) is, imo, a very, very valid way to program; but you're still very much in the driver's seat. It's not creating whole design patterns, etc, for you.

I wonder if maybe some people have been trying to jump on the "I have also tried vibe coding" train without being willing to hop as far as the term initiator defined it.

I definitely still stick to the "Vibe Coding is when you don't read / grok the code" definition.