CI/CD and security audits are activities that help with confidence and kicking the tires after development takes place, but the practice that's really needed he

CI/CD and security audits are activities that help with confidence and kicking the tires after development takes place, but the practice that's really needed here is scrutiny and review from the author of the change and from non-author peers while code is being put together. I'd go further and say that if the intent is to produce a production-ready, secure and well-designed and implemented solution, it cannot be vibe-coded. A prototype that de-risks the design and that gets trashed before implementation begins would be the right place for vibing.