You can never prove that there aren't any bugs. The definition can also change according to time and expectations.
I've made tens of internal developer tools because I couldn't gaf about using some third party vendor, all before vibe coding. Even then we purchased software from vendors, and we still do it now.
You can't cherry pick 2-3 pieces of problematic software, imply that it's how everything works. You're vibe coded Photoshop will never be used seriously, unfortunately. Same goes for the video editor, if you're fine with an autonomous AI agents listening to some internal github repo for issues that get auto or human reported and attempting to provide live fixes and feature enrichment, you aren't going to get that.
The problem really does stem from the fact that these agents, no matter how good you keep making them are still limited by a time horizon. AI companies have gotten really good at extending that horizon. The contexts get longer, prompts get less specific but theres a deadline to all of this. Take that LLM point it to a specific problem let it run, pull it out start new. The LLM will inevitably accumulate technical debt in it's own context, that starts to create a rot. You can try to improve this problem by making sub agents, etc. but you will 100% run into context rot after a period of time for the lead agent.