fix: use official vercel/action instead of amondnet/vercel-action to avoid --yes flag issues

.github/VERCEL_SETUP.md

@@ -0,0 +1,39 @@
+# Vercel Deployment Setup Guide
+
+## 🔧 **GitHub-Vercel Integration**
+
+This workflow uses GitHub's built-in Vercel integration, which means:
+- ✅ **No manual secrets required** - Uses `GITHUB_TOKEN` automatically
+- ✅ **Automatic authentication** - GitHub handles Vercel connection
+- ✅ **Built-in deployment tracking** - GitHub shows deployment stats
+
+## 🚀 **How It Works**
+
+The deployment workflow:
+1. **Uses `GITHUB_TOKEN`** - Automatically provided by GitHub Actions
+2. **Leverages GitHub-Vercel integration** - No additional setup needed
+3. **Deploys to Vercel** - Using the connected Vercel project
+4. **Shows deployment stats** - In GitHub's repository overview
+
+## 📋 **Setup Requirements**
+
+**Minimal setup needed:**
+1. Ensure Vercel app is connected to your GitHub repository
+2. The workflow will use GitHub's built-in Vercel integration
+3. No manual secrets or tokens required
+
+## 🎯 **Expected Results**
+
+Once the GitHub-Vercel integration is active:
+- ✅ Vercel deployments will work automatically
+- ✅ GitHub will show deployment stats and counts
+- ✅ Site will be deployed to: `https://prepguides-dev.vercel.app`
+- ✅ Preview deployments will work for PRs
+
+## 🔍 **Troubleshooting**
+
+If deployments fail:
+1. Check if Vercel app is connected to your GitHub repository
+2. Verify the repository has the correct permissions in Vercel
+3. Check GitHub Actions logs for specific error messages
+4. Ensure the Vercel project exists and is properly configured