Migrate from Railway to Vercel: fold API and worker into the web app, replace BullMQ with durable workflows

.env.example

@@ -1,8 +1,15 @@
-# Database
+# Database (Neon in production, plain Postgres locally)
+#
+# In production these are two DIFFERENT Neon endpoints, distinguished by
+# hostname rather than port: the pooled one carries a `-pooler` suffix.
+#   DATABASE_URL=postgresql://user:pass@ep-xxx-pooler.region.aws.neon.tech/overlap?sslmode=require
+#   DIRECT_URL=postgresql://user:pass@ep-xxx.region.aws.neon.tech/overlap?sslmode=require
+# Setting both to the same endpoint works until it does not: migrations need
+# the direct one, and the app needs the pooled one.
+#
+# Locally, a single Postgres accepts both.
 DATABASE_URL=postgresql://postgres:postgres@localhost:5432/overlap
-
-# Redis
-REDIS_URL=redis://localhost:6379
+DIRECT_URL=postgresql://postgres:postgres@localhost:5432/overlap
 
 # GitHub App
 GITHUB_APP_ID=
@@ -14,15 +21,14 @@ GITHUB_CLIENT_SECRET=
 # App
 SESSION_SECRET=
 APP_URL=http://localhost:3000
-API_URL=http://localhost:3001
 GITHUB_APP_SLUG=overlap-connector
+CRON_SECRET=
 
 # Web Push (VAPID)
 VAPID_PUBLIC_KEY=
 VAPID_PRIVATE_KEY=
-VAPID_SUBJECT=https://your-app-url.up.railway.app
+VAPID_SUBJECT=https://your-production-domain.example
 
 # Frontend (prefixed with VITE_ for client-side access)
-VITE_API_URL=http://localhost:3001
 VITE_GITHUB_APP_SLUG=overlap-connector
 VITE_VAPID_PUBLIC_KEY=

.gitignore

@@ -6,6 +6,7 @@ node_modules
 dist
 .next
 .output
+.vercel
 .turbo
 *.tsbuildinfo
 
@@ -35,3 +36,6 @@ coverage
 # Database
 drizzle/*.sql
 prod_dump.sql
+
+# Internal ship-run review transcripts
+.ship-fix-report.md

.ship/config.md

@@ -0,0 +1,6 @@
+# ship pipeline profile
+verify: npx turbo typecheck lint test --force && pnpm test:integration && pnpm --filter @overlap/web build  # asked
+base: main
+release: none
+post-merge: none
+pr-hook: none