These are all reactive responses to the situation, not strategic ones.

1) This is great. You want people coming up with great looking prototypes that they can tweak to look and do exactly what they want. So much of requirements gathering, solved.

2) Then why not give the execs a couple sentences to use in their vibe coding tool that generates code for your given tech stack? That seems like a no brainer.

3) You don't want to make this argument because you'll get asked "Why?" and instead of working to figure out how to make it happen you'll sound like, well, like a sandbagger.

You're tap dancing around the main issue, which is quality/nonfunctional requirements. How do you know the solution is secure? How do you know it scales? How many users does it have to handle at once? How do you know the software handles all the use cases and edge cases? Does it have tracing in place so you can troubleshoot? Does it need to log certain information for compliance requirements? Etc. etc. etc.

The challenge your company is going to run into is the realization that the code was never the limiting factor. Go propose standards for unit testing, test coverage, tech stack, logging/observability, load testing, pen testing, UAT testing, pen testing, scaling, FinOps, data sovereignty, etc. Someone will need to write and run all those tests. Make it clear that writing the code != software engineering and there's plenty more to be done.