Identified this app’s existing Vercel Functions in the pinned region as the managed executor that consumes Workflow routes. That let the recommendation name an exact worker without adding a second host. The live Functions platform was not deployed to; local Next production serving was used instead.
- What worked
- Repo evidence plus docs made the consumer concrete: the same Next.js deployment, via well-known workflow flow and step routes, rather than a new worker service.
