Prisma engine binary not bundled with workflow steps on Vercel

Hey, running into a Prisma + Vercel Workflow issue.

When a workflow step uses @prisma/client, the bundle at /var/task/index.js
ships without the engine binary next to it. Step crashes on first DB call.

Error:
PrismaClientInitializationError:
Invalid prisma.integration.findUnique() invocation:

Prisma Client could not locate the Query Engine for runtime "linux-arm64-openssl-3.0.x".

This is likely caused by a bundler that has not copied "libquery_engine-linux-arm64-openssl-3.0.x.so.node" next to the resulting bundle.
Ensure that "libquery_engine-linux-arm64-openssl-3.0.x.so.node" has been copied next to the bundle or in "node_modules/.prisma/client".

Same Prisma client works fine from regular API routes on the same deploy, only the workflow bundle is missing the .so.node.

Setup

• workflow@4.2.4, nuxt@3.13, prisma@5.19, @prisma/client@5.19
• Node 22 on Vercel
• binaryTargets = ["native", "rhel-openssl-3.0.x",
  "linux-arm64-openssl-3.0.x"]

Start by reproducing the workflow step with the listed workflow, Nuxt, Prisma, and Node versions, then inspect the generated /var/task/index.js bundle and node_modules/.prisma/client. Compare its contents with a regular API route, and verify that the linux-arm64-openssl-3.0.x engine is present and the database call succeeds in the workflow bundle.