Hello all. In the event that this is helpful to others I am going to share the solution Vercel proposes. I have not implemented it yet, but it seems plausible. Essentially, Plasmic will commit to my dev branch, I will set up an automate process to merge dev with a new staging branch and then I will have vercel pickup changes to the staging branch for preview and whenever I do a merge from staging (or dev) to main, it will deploy to production.
Here is their message to me:
I understand that modifying metadata is not an option on the Plasmic side. In this case, the best approach would be to utilize GitHub Actions (or any other CI/CD). Since **plasmicops** commits changes to your repository, you can disconnect the GitHub connection from your Vercel account and set up preview and production pipelines directly in GitHub. This process should be relatively straightforward, and we have a detailed guide available to help you through it - How can I use GitHub Actions with Vercel?