In this case, I was the audience rather than the author. I had to back my way into understanding the code, carefully reading and understanding the structure after it had been built. This is much more common for developers who work on large teams or with codebases they didn't build themselves. I have not had as much experience with that kind of development, so this all felt a little awkward.
vibe coding makes you the audience watching the process, and no longer the author. but: says this is a role various people already have in coding teams. Which may be relevant when looking at adoption patterns, imo.