Switch backend database wiring from Render Postgres to Supabase

[engdotme]

Summary

• Point Prisma at Supabase instead of the (now-unused) Render-managed
  Postgres instance. Adds directUrl to the Prisma datasource so
  prisma migrate deploy uses a session-mode connection while normal
  runtime queries go through a pooled connection.
• Update render.yaml to match: drop the databases: block and the
  fromDatabase wiring for DATABASE_URL (both pointed at the old
  Render Postgres), and declare DATABASE_URL/DIRECT_URL as
  dashboard-managed (sync: false) env vars instead.

Why

The backend's database was migrated to Supabase, but render.yaml
still auto-wired DATABASE_URL to Render's own Postgres resource,
causing prisma migrate deploy to fail with
database server` once that database was no longer in use.

Deploy notes (manual, outside this PR)

On the Render dashboard, forgeng-backend →

• DATABASE_URL → Supabase Transaction pooler string (port 6543)
• DIRECT_URL → Supabase Session pooler

Both must use Supabase's pooler hostnames, n
db.<ref>.supabase.co direct-connection host — that host is
IPv6-only, and Render's network doesn't supp
caused connections to hang indefinitely instead of failing fast.

Test plan

• Render deploy succeeds (`prisma migrat
• curl https://forgeng-backend.onrender.com/api/healthz returns
  {"status":"ok","database":"up"}
• Sign-up on https://forgeng-frontend.vercel.app/sign-up succeeds

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
forgeng-frontend	Ready	Preview, Comment	Jul 5, 2026 12:58pm

[github-actions]

Frontend coverage

Frontend coverage

Lines	Statements	Branches	Functions
	31.29% (819/2617)	24.61% (400/1625)	25.56% (192/751)

[github-actions]

Backend coverage

Backend coverage

Lines	Statements	Branches	Functions
	71.37% (1431/2005)	64.98% (850/1308)	73.64% (271/368)