Fresh deployments previously required manual schema setup because the database was built with drizzle-kit push (no migration tracking). This caused 500 errors when new columns were missing. The API now runs all pending Drizzle migrations before opening the connection pool, using a dedicated single-connection client that is closed immediately after. The Dockerfile copies the drizzle/ folder into the production image so migrations are always available.