incompatability with vercel workflows

[dywongcloud]

├
│ 1. OpenNext sets VERCEL=1 / VERCEL_DEPLOYMENT_ID for compat │
│ → withWorkflow takes the Vercel build path │
│ → import gets hashed: @workflow/world-vercel- │
│ → fails at runtime │
│ │
│ 2. WORKFLOW_NEXT_LAZY_DISCOVERY defaults on │
│ → routes resolved at runtime via dynamic import │
│ → that mechanism does not survive OpenNext transform │
│ → 404 for /.well-known/workflow/v1/flow │
│ │
│ 3. OpenNext strips dot-prefix directories from artifact │
│ → /.well-known/* routes don't exist at runtime even when │
│ generated eagerly │
│ │
│ 4. Next's rewrites() default to afterFiles │
│ → the eager .well-known route is still in the manifest, │
│ so Next tries to require its (stripped) handler before │
│ falling back to a rewrite