fix: let Vercel build remotely instead of building in Gitea runner

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

.gitea/workflows/deploy.yml

@@ -0,0 +1,31 @@
+name: Deploy to Vercel
+
+# Jab bhi 'revamp' branch pe push hoga, yeh automatically Vercel pe deploy kar dega.
+# Build Vercel ke servers pe hota hai (runner sirf code upload karta hai) — fast & reliable.
+on:
+  push:
+    branches:
+      - revamp
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    # Org aur Project ID secret nahi hain — yahin rakh diye taaki sirf VERCEL_TOKEN secret add karna pade
+    env:
+      VERCEL_ORG_ID: team_uSdJB1WvSXC3ilPP28AAsJ1z
+      VERCEL_PROJECT_ID: prj_frXDAngP1brs10g3lUsMa0xCBB9X
+      VERCEL_TOKEN: ${{ secrets.VERCEL_TOKEN }}
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: "22"
+
+      - name: Install Vercel CLI
+        run: npm install -g vercel@latest
+
+      - name: Deploy to production (Vercel builds remotely)
+        run: vercel deploy --prod --yes --token="$VERCEL_TOKEN"