Revert "Statically inject workflow world target" (#2752)

[VaguelySerious]

Reverts #2752 ("Statically inject workflow world target"). The world package is once again resolved at runtime from WORKFLOW_TARGET_WORLD instead of being aliased into host bundles at build time.

Why this is a surgical revert

141 commits have landed on top of #2752, several of which build on it, so git revert alone leaves the tree unbuildable. This branch removes the static-injection mechanism and restores the pre-#2752 runtime resolution while keeping everything that landed after it.

Removed

• world-target modules in @workflow/core, @workflow/builders, and the Statically inject workflow world target #2752 additions to @workflow/utils
• the bundler aliases / defines wired through next, nitro, nuxt, astro, sveltekit, rollup, and both nest builders
• the @workflow/core/runtime/world-target export, its tsconfig/vitest path aliases
• the pg-native stub alias and the extracted node-compat banner constants, which only existed because the world package was forced into the SSR bundle (the sveltekit typescript stub alias from fix(sveltekit): production server crash from bundled TypeScript compiler #2799 goes with them for the same reason)

Kept

• createWorldFromModule / WorldFactoryModule in core — still used by @workflow/world-testing and the nitro dev virtual handler
• world-init / world-init-stub / getWorldLazy and the globalThis[GetWorldFnKey] ??= getWorld registration, plus the test: regression coverage for hook.resume() from isolated route bundles (o2flow beta.26 incident) #3001 isolated-route-bundle regression test
• web: construct worlds explicitly instead of via static-injection stub #2804 (web), cli: restore dynamic world loading for community backends #2806 (cli dynamic community backends), Remove obsolete world factory aliases #3112 (world factory alias removal — core now imports createWorld from the world packages), [nest] Fix NestJS Vercel build output #2988 (nest vercel builder), Fix duplicate transforms of Nitro build artifacts #2925 / Fix Nitro cleanup for React Router and add setup guides #2908 (nitro), next basePath support, windows/canary test-timeout tuning

Note on the o2flow incident that motivated #2752

The o2flow failure (Cannot find module as expression is too dynamic on sandboxDoneHook.resume()) was caused by the world registration being tree-shaken out of an isolated route bundle, which made getWorldLazy() fall through to an obfuscated import() that Turbopack stubs. That path is fixed by the world-init side-effect import on every host entrypoint plus the loud "world runtime was not initialized" error — both of which this revert keeps, along with #3001's regression test. o2flow runs on the Vercel world, which core imports statically, so it never reaches the dynamic resolution path this revert restores.

A follow-up PR stacked on this one proposes hardening the remaining dynamic path (custom world packages under Turbopack/webpack) without reintroducing build-time injection.

Verification

• pnpm build, pnpm typecheck green
• unit tests for the affected packages green

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-nextjs-workflow-webpack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-astro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-express-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-fastify-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-hono-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nestjs-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nitro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nuxt-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-sveltekit-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-tanstack-start-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-vite-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-docs	Ready	Preview, Comment, Open in v0	Jul 29, 2026 6:18am
workflow-swc-playground	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-tarballs	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-web	Ready	Preview, Comment	Jul 29, 2026 6:18am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 164e7d3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 21 packages

Name	Type
@workflow/builders	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/nuxt	Patch
@workflow/astro	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/utils	Patch
@workflow/cli	Patch
@workflow/world-testing	Patch
@workflow/world-local	Patch
@workflow/world-vercel	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/vitest	Patch
@workflow/web-shared	Patch
@workflow/web	Patch
@workflow/errors	Patch
@workflow/world-postgres	Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

🧪 E2E Test Results

✅ All tests passed

E2E Test Summary

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	1455	0	239	1694
✅ 💻 Local Development	1621	0	227	1848
✅ 📦 Local Production	1621	0	227	1848
✅ 🐘 Local Postgres	1621	0	227	1848
✅ 🪟 Windows	154	0	0	154
✅ 📋 Other	1020	0	212	1232
✅ vercel-multi-region	27	0	0	27
Total	7519	0	1132	8651

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	126	0	28
✅ example	126	0	28
✅ express	126	0	28
✅ fastify	126	0	28
✅ hono	126	0	28
✅ nextjs-turbopack	151	0	3
✅ nextjs-webpack	151	0	3
✅ nitro	126	0	28
✅ nuxt	126	0	28
✅ sveltekit	145	0	9
✅ vite	126	0	28

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	154	0	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	128	0	26
✅ e2e-local-dev-tanstack-start-	128	0	26
✅ e2e-local-postgres-nest-stable	128	0	26
✅ e2e-local-postgres-tanstack-start-	128	0	26
✅ e2e-local-prod-nest-stable	128	0	26
✅ e2e-local-prod-tanstack-start-	128	0	26
✅ e2e-vercel-prod-nest	126	0	28
✅ e2e-vercel-prod-tanstack-start	126	0	28

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

---

📋 View full workflow run

[github-actions]

📊 Workflow Benchmarks

commit 164e7d3 · Wed, 29 Jul 2026 06:36:12 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	424 (-39%) 💚	1299 🔴 (+26%) 🔻	1315 🔴 (+24%) 🔻	1415 🔴 (-15%)	30
TTFS	stream	1251 (+30%) 🔻	1316 🔴 (+29%) 🔻	1330 🔴 (+28%) 🔻	1428 🔴 (+23%) 🔻	30
TTFS	hook + stream	1482 (+26%) 🔻	1532 🔴 (+18%) 🔻	1597 🔴 (+17%) 🔻	1953 🔴 (+27%) 🔻	30
STSO	1020 steps (1-20)	166 (-8.8%)	254 🔴 (-3.4%)	290 🔴 (-11%)	313 🔴 (-17%) 💚	19
STSO	1020 steps (101-120)	186 (-2.6%)	241 🔴 (-8.0%)	270 🔴 (-18%) 💚	378 🔴 (-64%) 💚	19
STSO	1020 steps (1001-1020)	477 (+1.5%)	583 🔴 (+4.1%)	676 🔴 (-3.3%)	717 🔴 (-6.6%)	19
WO	1020 steps	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	1
SL	stream latency	96 (+22%) 🔻	142 🔴 (+12%)	162 🔴 (+3.8%)	181 🔴 (-18%) 💚	30
SO	stream overhead (text)	95 (-13%)	210 (±0%)	350 (+10%)	3151 🔴 (+399%) 🔻	30
SO	stream overhead (structured)	98 (-2.0%)	144 (-17%) 💚	160 (-18%) 💚	240 (-43%) 💚	30

📜 Previous results (1)

003f800

Mon, 27 Jul 2026 22:42:23 GMT · run logs

vercel / nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	238 (-68%) 💚	1374 🔴 (+21%) 🔻	1408 🔴 (+16%) 🔻	1708 🔴 (+25%) 🔻	30
TTFS	stream	242 (-23%) 💚	1347 🔴 (+23%) 🔻	1384 🔴 (+21%) 🔻	1396 🔴 (+19%) 🔻	30
TTFS	hook + stream	400 (-68%) 💚	1555 🔴 (+11%)	1601 🔴 (+9.6%)	1624 🔴 (-0.7%)	30
STSO	1020 steps (1-20)	167 (-1.8%)	273 🔴 (-9.6%)	283 🔴 (-20%) 💚	347 🔴 (-8.4%)	19
STSO	1020 steps (101-120)	206 (+4.6%)	302 🔴 (-11%)	477 🔴 (+17%) 🔻	2242 🔴 (+348%) 🔻	19
STSO	1020 steps (1001-1020)	472 (-2.3%)	551 🔴 (-4.0%)	591 🔴 (-8.5%)	1103 🔴 (+68%) 🔻	19
WO	1020 steps	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	1
SL	stream latency	101 (+8.6%)	148 🔴 (-12%)	179 🔴 (-24%) 💚	250 🔴 (-1.2%)	30
SO	stream overhead (text)	115 (-12%)	185 (-36%) 💚	209 (-41%) 💚	401 (-4.8%)	30
SO	stream overhead (structured)	124 (-8.1%)	209 (-20%) 💚	256 (-7.9%)	430 (+4.1%)	30

ℹ️ Metric definitions & methodology

_{Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.}

_{Metrics — TTFS: time to first step body (in-deployment start() → first step body, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)}

_{Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost}

_{🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120}

_{All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.}

_{Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.}

[github-actions]

No backport to stable for a09d001 (AI decision).

This commit reverts #2752 (static world-target injection), which only ever landed on main — origin/stable has no packages/core/src/runtime/world-target.ts, no packages/builders/src/world-target.ts, no packages/core/vitest.config.ts world-target alias, and its packages/core/src/runtime/world.ts / packages/utils/src/world-target.ts already resolve the world at runtime from WORKFLOW_TARGET_WORLD, i.e. exactly the behavior this revert restores. Backporting a revert of something absent from stable would only churn unrelated files (nitro/next/sveltekit builder changes, workbench configs, v5 docs) with no corresponding defect fix.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

a09d00135bd96f22bd1ae1dee6b5a6f797b7d804

[VaguelySerious]

Reverts #2752 ("Statically inject workflow world target"). The world package is once again resolved at runtime from WORKFLOW_TARGET_WORLD instead of being aliased into host bundles at build time.

Why this is a surgical revert

141 commits have landed on top of #2752, several of which build on it, so git revert alone leaves the tree unbuildable. This branch removes the static-injection mechanism and restores the pre-#2752 runtime resolution while keeping everything that landed after it.

Removed

• world-target modules in @workflow/core, @workflow/builders, and the Statically inject workflow world target #2752 additions to @workflow/utils
• the bundler aliases / defines wired through next, nitro, nuxt, astro, sveltekit, rollup, and both nest builders
• the @workflow/core/runtime/world-target export, its tsconfig/vitest path aliases
• the pg-native stub alias and the extracted node-compat banner constants, which only existed because the world package was forced into the SSR bundle (the sveltekit typescript stub alias from fix(sveltekit): production server crash from bundled TypeScript compiler #2799 goes with them for the same reason)

Kept

• createWorldFromModule / WorldFactoryModule in core — still used by @workflow/world-testing and the nitro dev virtual handler
• world-init / world-init-stub / getWorldLazy and the globalThis[GetWorldFnKey] ??= getWorld registration, plus the test: regression coverage for hook.resume() from isolated route bundles (o2flow beta.26 incident) #3001 isolated-route-bundle regression test
• web: construct worlds explicitly instead of via static-injection stub #2804 (web), cli: restore dynamic world loading for community backends #2806 (cli dynamic community backends), Remove obsolete world factory aliases #3112 (world factory alias removal — core now imports createWorld from the world packages), [nest] Fix NestJS Vercel build output #2988 (nest vercel builder), Fix duplicate transforms of Nitro build artifacts #2925 / Fix Nitro cleanup for React Router and add setup guides #2908 (nitro), next basePath support, windows/canary test-timeout tuning

Note on the o2flow incident that motivated #2752

The o2flow failure (Cannot find module as expression is too dynamic on sandboxDoneHook.resume()) was caused by the world registration being tree-shaken out of an isolated route bundle, which made getWorldLazy() fall through to an obfuscated import() that Turbopack stubs. That path is fixed by the world-init side-effect import on every host entrypoint plus the loud "world runtime was not initialized" error — both of which this revert keeps, along with #3001's regression test. o2flow runs on the Vercel world, which core imports statically, so it never reaches the dynamic resolution path this revert restores.

A follow-up PR stacked on this one proposes hardening the remaining dynamic path (custom world packages under Turbopack/webpack) without reintroducing build-time injection.

Verification

• pnpm build, pnpm typecheck green
• unit tests for the affected packages green

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-nextjs-workflow-webpack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-astro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-express-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-fastify-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-hono-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nestjs-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nitro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nuxt-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-sveltekit-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-tanstack-start-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-vite-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-docs	Ready	Preview, Comment, Open in v0	Jul 29, 2026 6:18am
workflow-swc-playground	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-tarballs	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-web	Ready	Preview, Comment	Jul 29, 2026 6:18am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 164e7d3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 21 packages

Name	Type
@workflow/builders	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/nuxt	Patch
@workflow/astro	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/utils	Patch
@workflow/cli	Patch
@workflow/world-testing	Patch
@workflow/world-local	Patch
@workflow/world-vercel	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/vitest	Patch
@workflow/web-shared	Patch
@workflow/web	Patch
@workflow/errors	Patch
@workflow/world-postgres	Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

🧪 E2E Test Results

✅ All tests passed

E2E Test Summary

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	1455	0	239	1694
✅ 💻 Local Development	1621	0	227	1848
✅ 📦 Local Production	1621	0	227	1848
✅ 🐘 Local Postgres	1621	0	227	1848
✅ 🪟 Windows	154	0	0	154
✅ 📋 Other	1020	0	212	1232
✅ vercel-multi-region	27	0	0	27
Total	7519	0	1132	8651

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	126	0	28
✅ example	126	0	28
✅ express	126	0	28
✅ fastify	126	0	28
✅ hono	126	0	28
✅ nextjs-turbopack	151	0	3
✅ nextjs-webpack	151	0	3
✅ nitro	126	0	28
✅ nuxt	126	0	28
✅ sveltekit	145	0	9
✅ vite	126	0	28

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	154	0	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	128	0	26
✅ e2e-local-dev-tanstack-start-	128	0	26
✅ e2e-local-postgres-nest-stable	128	0	26
✅ e2e-local-postgres-tanstack-start-	128	0	26
✅ e2e-local-prod-nest-stable	128	0	26
✅ e2e-local-prod-tanstack-start-	128	0	26
✅ e2e-vercel-prod-nest	126	0	28
✅ e2e-vercel-prod-tanstack-start	126	0	28

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

---

📋 View full workflow run

[github-actions]

📊 Workflow Benchmarks

commit 164e7d3 · Wed, 29 Jul 2026 06:36:12 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	424 (-39%) 💚	1299 🔴 (+26%) 🔻	1315 🔴 (+24%) 🔻	1415 🔴 (-15%)	30
TTFS	stream	1251 (+30%) 🔻	1316 🔴 (+29%) 🔻	1330 🔴 (+28%) 🔻	1428 🔴 (+23%) 🔻	30
TTFS	hook + stream	1482 (+26%) 🔻	1532 🔴 (+18%) 🔻	1597 🔴 (+17%) 🔻	1953 🔴 (+27%) 🔻	30
STSO	1020 steps (1-20)	166 (-8.8%)	254 🔴 (-3.4%)	290 🔴 (-11%)	313 🔴 (-17%) 💚	19
STSO	1020 steps (101-120)	186 (-2.6%)	241 🔴 (-8.0%)	270 🔴 (-18%) 💚	378 🔴 (-64%) 💚	19
STSO	1020 steps (1001-1020)	477 (+1.5%)	583 🔴 (+4.1%)	676 🔴 (-3.3%)	717 🔴 (-6.6%)	19
WO	1020 steps	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	1
SL	stream latency	96 (+22%) 🔻	142 🔴 (+12%)	162 🔴 (+3.8%)	181 🔴 (-18%) 💚	30
SO	stream overhead (text)	95 (-13%)	210 (±0%)	350 (+10%)	3151 🔴 (+399%) 🔻	30
SO	stream overhead (structured)	98 (-2.0%)	144 (-17%) 💚	160 (-18%) 💚	240 (-43%) 💚	30

📜 Previous results (1)

003f800

Mon, 27 Jul 2026 22:42:23 GMT · run logs

vercel / nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	238 (-68%) 💚	1374 🔴 (+21%) 🔻	1408 🔴 (+16%) 🔻	1708 🔴 (+25%) 🔻	30
TTFS	stream	242 (-23%) 💚	1347 🔴 (+23%) 🔻	1384 🔴 (+21%) 🔻	1396 🔴 (+19%) 🔻	30
TTFS	hook + stream	400 (-68%) 💚	1555 🔴 (+11%)	1601 🔴 (+9.6%)	1624 🔴 (-0.7%)	30
STSO	1020 steps (1-20)	167 (-1.8%)	273 🔴 (-9.6%)	283 🔴 (-20%) 💚	347 🔴 (-8.4%)	19
STSO	1020 steps (101-120)	206 (+4.6%)	302 🔴 (-11%)	477 🔴 (+17%) 🔻	2242 🔴 (+348%) 🔻	19
STSO	1020 steps (1001-1020)	472 (-2.3%)	551 🔴 (-4.0%)	591 🔴 (-8.5%)	1103 🔴 (+68%) 🔻	19
WO	1020 steps	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	1
SL	stream latency	101 (+8.6%)	148 🔴 (-12%)	179 🔴 (-24%) 💚	250 🔴 (-1.2%)	30
SO	stream overhead (text)	115 (-12%)	185 (-36%) 💚	209 (-41%) 💚	401 (-4.8%)	30
SO	stream overhead (structured)	124 (-8.1%)	209 (-20%) 💚	256 (-7.9%)	430 (+4.1%)	30

ℹ️ Metric definitions & methodology

_{Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.}

_{Metrics — TTFS: time to first step body (in-deployment start() → first step body, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)}

_{Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost}

_{🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120}

_{All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.}

_{Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.}

[github-actions]

No backport to stable for a09d001 (AI decision).

This commit reverts #2752 (static world-target injection), which only ever landed on main — origin/stable has no packages/core/src/runtime/world-target.ts, no packages/builders/src/world-target.ts, no packages/core/vitest.config.ts world-target alias, and its packages/core/src/runtime/world.ts / packages/utils/src/world-target.ts already resolve the world at runtime from WORKFLOW_TARGET_WORLD, i.e. exactly the behavior this revert restores. Backporting a revert of something absent from stable would only churn unrelated files (nitro/next/sveltekit builder changes, workbench configs, v5 docs) with no corresponding defect fix.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

a09d00135bd96f22bd1ae1dee6b5a6f797b7d804

[VaguelySerious]

Reverts #2752 ("Statically inject workflow world target"). The world package is once again resolved at runtime from WORKFLOW_TARGET_WORLD instead of being aliased into host bundles at build time.

Why this is a surgical revert

141 commits have landed on top of #2752, several of which build on it, so git revert alone leaves the tree unbuildable. This branch removes the static-injection mechanism and restores the pre-#2752 runtime resolution while keeping everything that landed after it.

Removed

• world-target modules in @workflow/core, @workflow/builders, and the Statically inject workflow world target #2752 additions to @workflow/utils
• the bundler aliases / defines wired through next, nitro, nuxt, astro, sveltekit, rollup, and both nest builders
• the @workflow/core/runtime/world-target export, its tsconfig/vitest path aliases
• the pg-native stub alias and the extracted node-compat banner constants, which only existed because the world package was forced into the SSR bundle (the sveltekit typescript stub alias from fix(sveltekit): production server crash from bundled TypeScript compiler #2799 goes with them for the same reason)

Kept

• createWorldFromModule / WorldFactoryModule in core — still used by @workflow/world-testing and the nitro dev virtual handler
• world-init / world-init-stub / getWorldLazy and the globalThis[GetWorldFnKey] ??= getWorld registration, plus the test: regression coverage for hook.resume() from isolated route bundles (o2flow beta.26 incident) #3001 isolated-route-bundle regression test
• web: construct worlds explicitly instead of via static-injection stub #2804 (web), cli: restore dynamic world loading for community backends #2806 (cli dynamic community backends), Remove obsolete world factory aliases #3112 (world factory alias removal — core now imports createWorld from the world packages), [nest] Fix NestJS Vercel build output #2988 (nest vercel builder), Fix duplicate transforms of Nitro build artifacts #2925 / Fix Nitro cleanup for React Router and add setup guides #2908 (nitro), next basePath support, windows/canary test-timeout tuning

Note on the o2flow incident that motivated #2752

The o2flow failure (Cannot find module as expression is too dynamic on sandboxDoneHook.resume()) was caused by the world registration being tree-shaken out of an isolated route bundle, which made getWorldLazy() fall through to an obfuscated import() that Turbopack stubs. That path is fixed by the world-init side-effect import on every host entrypoint plus the loud "world runtime was not initialized" error — both of which this revert keeps, along with #3001's regression test. o2flow runs on the Vercel world, which core imports statically, so it never reaches the dynamic resolution path this revert restores.

A follow-up PR stacked on this one proposes hardening the remaining dynamic path (custom world packages under Turbopack/webpack) without reintroducing build-time injection.

Verification

• pnpm build, pnpm typecheck green
• unit tests for the affected packages green

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-nextjs-workflow-webpack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-astro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-express-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-fastify-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-hono-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nestjs-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nitro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nuxt-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-sveltekit-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-tanstack-start-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-vite-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-docs	Ready	Preview, Comment, Open in v0	Jul 29, 2026 6:18am
workflow-swc-playground	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-tarballs	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-web	Ready	Preview, Comment	Jul 29, 2026 6:18am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 164e7d3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 21 packages

Name	Type
@workflow/builders	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/nuxt	Patch
@workflow/astro	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/utils	Patch
@workflow/cli	Patch
@workflow/world-testing	Patch
@workflow/world-local	Patch
@workflow/world-vercel	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/vitest	Patch
@workflow/web-shared	Patch
@workflow/web	Patch
@workflow/errors	Patch
@workflow/world-postgres	Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

🧪 E2E Test Results

✅ All tests passed

E2E Test Summary

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	1455	0	239	1694
✅ 💻 Local Development	1621	0	227	1848
✅ 📦 Local Production	1621	0	227	1848
✅ 🐘 Local Postgres	1621	0	227	1848
✅ 🪟 Windows	154	0	0	154
✅ 📋 Other	1020	0	212	1232
✅ vercel-multi-region	27	0	0	27
Total	7519	0	1132	8651

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	126	0	28
✅ example	126	0	28
✅ express	126	0	28
✅ fastify	126	0	28
✅ hono	126	0	28
✅ nextjs-turbopack	151	0	3
✅ nextjs-webpack	151	0	3
✅ nitro	126	0	28
✅ nuxt	126	0	28
✅ sveltekit	145	0	9
✅ vite	126	0	28

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	154	0	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	128	0	26
✅ e2e-local-dev-tanstack-start-	128	0	26
✅ e2e-local-postgres-nest-stable	128	0	26
✅ e2e-local-postgres-tanstack-start-	128	0	26
✅ e2e-local-prod-nest-stable	128	0	26
✅ e2e-local-prod-tanstack-start-	128	0	26
✅ e2e-vercel-prod-nest	126	0	28
✅ e2e-vercel-prod-tanstack-start	126	0	28

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

---

📋 View full workflow run

[github-actions]

📊 Workflow Benchmarks

commit 164e7d3 · Wed, 29 Jul 2026 06:36:12 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	424 (-39%) 💚	1299 🔴 (+26%) 🔻	1315 🔴 (+24%) 🔻	1415 🔴 (-15%)	30
TTFS	stream	1251 (+30%) 🔻	1316 🔴 (+29%) 🔻	1330 🔴 (+28%) 🔻	1428 🔴 (+23%) 🔻	30
TTFS	hook + stream	1482 (+26%) 🔻	1532 🔴 (+18%) 🔻	1597 🔴 (+17%) 🔻	1953 🔴 (+27%) 🔻	30
STSO	1020 steps (1-20)	166 (-8.8%)	254 🔴 (-3.4%)	290 🔴 (-11%)	313 🔴 (-17%) 💚	19
STSO	1020 steps (101-120)	186 (-2.6%)	241 🔴 (-8.0%)	270 🔴 (-18%) 💚	378 🔴 (-64%) 💚	19
STSO	1020 steps (1001-1020)	477 (+1.5%)	583 🔴 (+4.1%)	676 🔴 (-3.3%)	717 🔴 (-6.6%)	19
WO	1020 steps	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	1
SL	stream latency	96 (+22%) 🔻	142 🔴 (+12%)	162 🔴 (+3.8%)	181 🔴 (-18%) 💚	30
SO	stream overhead (text)	95 (-13%)	210 (±0%)	350 (+10%)	3151 🔴 (+399%) 🔻	30
SO	stream overhead (structured)	98 (-2.0%)	144 (-17%) 💚	160 (-18%) 💚	240 (-43%) 💚	30

📜 Previous results (1)

003f800

Mon, 27 Jul 2026 22:42:23 GMT · run logs

vercel / nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	238 (-68%) 💚	1374 🔴 (+21%) 🔻	1408 🔴 (+16%) 🔻	1708 🔴 (+25%) 🔻	30
TTFS	stream	242 (-23%) 💚	1347 🔴 (+23%) 🔻	1384 🔴 (+21%) 🔻	1396 🔴 (+19%) 🔻	30
TTFS	hook + stream	400 (-68%) 💚	1555 🔴 (+11%)	1601 🔴 (+9.6%)	1624 🔴 (-0.7%)	30
STSO	1020 steps (1-20)	167 (-1.8%)	273 🔴 (-9.6%)	283 🔴 (-20%) 💚	347 🔴 (-8.4%)	19
STSO	1020 steps (101-120)	206 (+4.6%)	302 🔴 (-11%)	477 🔴 (+17%) 🔻	2242 🔴 (+348%) 🔻	19
STSO	1020 steps (1001-1020)	472 (-2.3%)	551 🔴 (-4.0%)	591 🔴 (-8.5%)	1103 🔴 (+68%) 🔻	19
WO	1020 steps	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	1
SL	stream latency	101 (+8.6%)	148 🔴 (-12%)	179 🔴 (-24%) 💚	250 🔴 (-1.2%)	30
SO	stream overhead (text)	115 (-12%)	185 (-36%) 💚	209 (-41%) 💚	401 (-4.8%)	30
SO	stream overhead (structured)	124 (-8.1%)	209 (-20%) 💚	256 (-7.9%)	430 (+4.1%)	30

ℹ️ Metric definitions & methodology

_{Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.}

_{Metrics — TTFS: time to first step body (in-deployment start() → first step body, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)}

_{Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost}

_{🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120}

_{All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.}

_{Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.}

[github-actions]

No backport to stable for a09d001 (AI decision).

This commit reverts #2752 (static world-target injection), which only ever landed on main — origin/stable has no packages/core/src/runtime/world-target.ts, no packages/builders/src/world-target.ts, no packages/core/vitest.config.ts world-target alias, and its packages/core/src/runtime/world.ts / packages/utils/src/world-target.ts already resolve the world at runtime from WORKFLOW_TARGET_WORLD, i.e. exactly the behavior this revert restores. Backporting a revert of something absent from stable would only churn unrelated files (nitro/next/sveltekit builder changes, workbench configs, v5 docs) with no corresponding defect fix.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

a09d00135bd96f22bd1ae1dee6b5a6f797b7d804

[VaguelySerious]

Reverts #2752 ("Statically inject workflow world target"). The world package is once again resolved at runtime from WORKFLOW_TARGET_WORLD instead of being aliased into host bundles at build time.

Why this is a surgical revert

141 commits have landed on top of #2752, several of which build on it, so git revert alone leaves the tree unbuildable. This branch removes the static-injection mechanism and restores the pre-#2752 runtime resolution while keeping everything that landed after it.

Removed

• world-target modules in @workflow/core, @workflow/builders, and the Statically inject workflow world target #2752 additions to @workflow/utils
• the bundler aliases / defines wired through next, nitro, nuxt, astro, sveltekit, rollup, and both nest builders
• the @workflow/core/runtime/world-target export, its tsconfig/vitest path aliases
• the pg-native stub alias and the extracted node-compat banner constants, which only existed because the world package was forced into the SSR bundle (the sveltekit typescript stub alias from fix(sveltekit): production server crash from bundled TypeScript compiler #2799 goes with them for the same reason)

Kept

• createWorldFromModule / WorldFactoryModule in core — still used by @workflow/world-testing and the nitro dev virtual handler
• world-init / world-init-stub / getWorldLazy and the globalThis[GetWorldFnKey] ??= getWorld registration, plus the test: regression coverage for hook.resume() from isolated route bundles (o2flow beta.26 incident) #3001 isolated-route-bundle regression test
• web: construct worlds explicitly instead of via static-injection stub #2804 (web), cli: restore dynamic world loading for community backends #2806 (cli dynamic community backends), Remove obsolete world factory aliases #3112 (world factory alias removal — core now imports createWorld from the world packages), [nest] Fix NestJS Vercel build output #2988 (nest vercel builder), Fix duplicate transforms of Nitro build artifacts #2925 / Fix Nitro cleanup for React Router and add setup guides #2908 (nitro), next basePath support, windows/canary test-timeout tuning

Note on the o2flow incident that motivated #2752

The o2flow failure (Cannot find module as expression is too dynamic on sandboxDoneHook.resume()) was caused by the world registration being tree-shaken out of an isolated route bundle, which made getWorldLazy() fall through to an obfuscated import() that Turbopack stubs. That path is fixed by the world-init side-effect import on every host entrypoint plus the loud "world runtime was not initialized" error — both of which this revert keeps, along with #3001's regression test. o2flow runs on the Vercel world, which core imports statically, so it never reaches the dynamic resolution path this revert restores.

A follow-up PR stacked on this one proposes hardening the remaining dynamic path (custom world packages under Turbopack/webpack) without reintroducing build-time injection.

Verification

• pnpm build, pnpm typecheck green
• unit tests for the affected packages green

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-nextjs-workflow-webpack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-astro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-express-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-fastify-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-hono-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nestjs-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nitro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nuxt-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-sveltekit-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-tanstack-start-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-vite-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-docs	Ready	Preview, Comment, Open in v0	Jul 29, 2026 6:18am
workflow-swc-playground	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-tarballs	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-web	Ready	Preview, Comment	Jul 29, 2026 6:18am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 164e7d3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 21 packages

Name	Type
@workflow/builders	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/nuxt	Patch
@workflow/astro	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/utils	Patch
@workflow/cli	Patch
@workflow/world-testing	Patch
@workflow/world-local	Patch
@workflow/world-vercel	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/vitest	Patch
@workflow/web-shared	Patch
@workflow/web	Patch
@workflow/errors	Patch
@workflow/world-postgres	Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

🧪 E2E Test Results

✅ All tests passed

E2E Test Summary

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	1455	0	239	1694
✅ 💻 Local Development	1621	0	227	1848
✅ 📦 Local Production	1621	0	227	1848
✅ 🐘 Local Postgres	1621	0	227	1848
✅ 🪟 Windows	154	0	0	154
✅ 📋 Other	1020	0	212	1232
✅ vercel-multi-region	27	0	0	27
Total	7519	0	1132	8651

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	126	0	28
✅ example	126	0	28
✅ express	126	0	28
✅ fastify	126	0	28
✅ hono	126	0	28
✅ nextjs-turbopack	151	0	3
✅ nextjs-webpack	151	0	3
✅ nitro	126	0	28
✅ nuxt	126	0	28
✅ sveltekit	145	0	9
✅ vite	126	0	28

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	154	0	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	128	0	26
✅ e2e-local-dev-tanstack-start-	128	0	26
✅ e2e-local-postgres-nest-stable	128	0	26
✅ e2e-local-postgres-tanstack-start-	128	0	26
✅ e2e-local-prod-nest-stable	128	0	26
✅ e2e-local-prod-tanstack-start-	128	0	26
✅ e2e-vercel-prod-nest	126	0	28
✅ e2e-vercel-prod-tanstack-start	126	0	28

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

---

📋 View full workflow run

[github-actions]

📊 Workflow Benchmarks

commit 164e7d3 · Wed, 29 Jul 2026 06:36:12 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	424 (-39%) 💚	1299 🔴 (+26%) 🔻	1315 🔴 (+24%) 🔻	1415 🔴 (-15%)	30
TTFS	stream	1251 (+30%) 🔻	1316 🔴 (+29%) 🔻	1330 🔴 (+28%) 🔻	1428 🔴 (+23%) 🔻	30
TTFS	hook + stream	1482 (+26%) 🔻	1532 🔴 (+18%) 🔻	1597 🔴 (+17%) 🔻	1953 🔴 (+27%) 🔻	30
STSO	1020 steps (1-20)	166 (-8.8%)	254 🔴 (-3.4%)	290 🔴 (-11%)	313 🔴 (-17%) 💚	19
STSO	1020 steps (101-120)	186 (-2.6%)	241 🔴 (-8.0%)	270 🔴 (-18%) 💚	378 🔴 (-64%) 💚	19
STSO	1020 steps (1001-1020)	477 (+1.5%)	583 🔴 (+4.1%)	676 🔴 (-3.3%)	717 🔴 (-6.6%)	19
WO	1020 steps	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	1
SL	stream latency	96 (+22%) 🔻	142 🔴 (+12%)	162 🔴 (+3.8%)	181 🔴 (-18%) 💚	30
SO	stream overhead (text)	95 (-13%)	210 (±0%)	350 (+10%)	3151 🔴 (+399%) 🔻	30
SO	stream overhead (structured)	98 (-2.0%)	144 (-17%) 💚	160 (-18%) 💚	240 (-43%) 💚	30

📜 Previous results (1)

003f800

Mon, 27 Jul 2026 22:42:23 GMT · run logs

vercel / nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	238 (-68%) 💚	1374 🔴 (+21%) 🔻	1408 🔴 (+16%) 🔻	1708 🔴 (+25%) 🔻	30
TTFS	stream	242 (-23%) 💚	1347 🔴 (+23%) 🔻	1384 🔴 (+21%) 🔻	1396 🔴 (+19%) 🔻	30
TTFS	hook + stream	400 (-68%) 💚	1555 🔴 (+11%)	1601 🔴 (+9.6%)	1624 🔴 (-0.7%)	30
STSO	1020 steps (1-20)	167 (-1.8%)	273 🔴 (-9.6%)	283 🔴 (-20%) 💚	347 🔴 (-8.4%)	19
STSO	1020 steps (101-120)	206 (+4.6%)	302 🔴 (-11%)	477 🔴 (+17%) 🔻	2242 🔴 (+348%) 🔻	19
STSO	1020 steps (1001-1020)	472 (-2.3%)	551 🔴 (-4.0%)	591 🔴 (-8.5%)	1103 🔴 (+68%) 🔻	19
WO	1020 steps	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	1
SL	stream latency	101 (+8.6%)	148 🔴 (-12%)	179 🔴 (-24%) 💚	250 🔴 (-1.2%)	30
SO	stream overhead (text)	115 (-12%)	185 (-36%) 💚	209 (-41%) 💚	401 (-4.8%)	30
SO	stream overhead (structured)	124 (-8.1%)	209 (-20%) 💚	256 (-7.9%)	430 (+4.1%)	30

ℹ️ Metric definitions & methodology

_{Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.}

_{Metrics — TTFS: time to first step body (in-deployment start() → first step body, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)}

_{Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost}

_{🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120}

_{All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.}

_{Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.}

[github-actions]

No backport to stable for a09d001 (AI decision).

This commit reverts #2752 (static world-target injection), which only ever landed on main — origin/stable has no packages/core/src/runtime/world-target.ts, no packages/builders/src/world-target.ts, no packages/core/vitest.config.ts world-target alias, and its packages/core/src/runtime/world.ts / packages/utils/src/world-target.ts already resolve the world at runtime from WORKFLOW_TARGET_WORLD, i.e. exactly the behavior this revert restores. Backporting a revert of something absent from stable would only churn unrelated files (nitro/next/sveltekit builder changes, workbench configs, v5 docs) with no corresponding defect fix.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

a09d00135bd96f22bd1ae1dee6b5a6f797b7d804

[VaguelySerious]

Reverts #2752 ("Statically inject workflow world target"). The world package is once again resolved at runtime from WORKFLOW_TARGET_WORLD instead of being aliased into host bundles at build time.

Why this is a surgical revert

141 commits have landed on top of #2752, several of which build on it, so git revert alone leaves the tree unbuildable. This branch removes the static-injection mechanism and restores the pre-#2752 runtime resolution while keeping everything that landed after it.

Removed

• world-target modules in @workflow/core, @workflow/builders, and the Statically inject workflow world target #2752 additions to @workflow/utils
• the bundler aliases / defines wired through next, nitro, nuxt, astro, sveltekit, rollup, and both nest builders
• the @workflow/core/runtime/world-target export, its tsconfig/vitest path aliases
• the pg-native stub alias and the extracted node-compat banner constants, which only existed because the world package was forced into the SSR bundle (the sveltekit typescript stub alias from fix(sveltekit): production server crash from bundled TypeScript compiler #2799 goes with them for the same reason)

Kept

• createWorldFromModule / WorldFactoryModule in core — still used by @workflow/world-testing and the nitro dev virtual handler
• world-init / world-init-stub / getWorldLazy and the globalThis[GetWorldFnKey] ??= getWorld registration, plus the test: regression coverage for hook.resume() from isolated route bundles (o2flow beta.26 incident) #3001 isolated-route-bundle regression test
• web: construct worlds explicitly instead of via static-injection stub #2804 (web), cli: restore dynamic world loading for community backends #2806 (cli dynamic community backends), Remove obsolete world factory aliases #3112 (world factory alias removal — core now imports createWorld from the world packages), [nest] Fix NestJS Vercel build output #2988 (nest vercel builder), Fix duplicate transforms of Nitro build artifacts #2925 / Fix Nitro cleanup for React Router and add setup guides #2908 (nitro), next basePath support, windows/canary test-timeout tuning

Note on the o2flow incident that motivated #2752

The o2flow failure (Cannot find module as expression is too dynamic on sandboxDoneHook.resume()) was caused by the world registration being tree-shaken out of an isolated route bundle, which made getWorldLazy() fall through to an obfuscated import() that Turbopack stubs. That path is fixed by the world-init side-effect import on every host entrypoint plus the loud "world runtime was not initialized" error — both of which this revert keeps, along with #3001's regression test. o2flow runs on the Vercel world, which core imports statically, so it never reaches the dynamic resolution path this revert restores.

A follow-up PR stacked on this one proposes hardening the remaining dynamic path (custom world packages under Turbopack/webpack) without reintroducing build-time injection.

Verification

• pnpm build, pnpm typecheck green
• unit tests for the affected packages green

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-nextjs-workflow-webpack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-astro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-express-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-fastify-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-hono-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nestjs-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nitro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nuxt-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-sveltekit-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-tanstack-start-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-vite-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-docs	Ready	Preview, Comment, Open in v0	Jul 29, 2026 6:18am
workflow-swc-playground	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-tarballs	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-web	Ready	Preview, Comment	Jul 29, 2026 6:18am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 164e7d3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 21 packages

Name	Type
@workflow/builders	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/nuxt	Patch
@workflow/astro	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/utils	Patch
@workflow/cli	Patch
@workflow/world-testing	Patch
@workflow/world-local	Patch
@workflow/world-vercel	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/vitest	Patch
@workflow/web-shared	Patch
@workflow/web	Patch
@workflow/errors	Patch
@workflow/world-postgres	Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

🧪 E2E Test Results

✅ All tests passed

E2E Test Summary

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	1455	0	239	1694
✅ 💻 Local Development	1621	0	227	1848
✅ 📦 Local Production	1621	0	227	1848
✅ 🐘 Local Postgres	1621	0	227	1848
✅ 🪟 Windows	154	0	0	154
✅ 📋 Other	1020	0	212	1232
✅ vercel-multi-region	27	0	0	27
Total	7519	0	1132	8651

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	126	0	28
✅ example	126	0	28
✅ express	126	0	28
✅ fastify	126	0	28
✅ hono	126	0	28
✅ nextjs-turbopack	151	0	3
✅ nextjs-webpack	151	0	3
✅ nitro	126	0	28
✅ nuxt	126	0	28
✅ sveltekit	145	0	9
✅ vite	126	0	28

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	154	0	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	128	0	26
✅ e2e-local-dev-tanstack-start-	128	0	26
✅ e2e-local-postgres-nest-stable	128	0	26
✅ e2e-local-postgres-tanstack-start-	128	0	26
✅ e2e-local-prod-nest-stable	128	0	26
✅ e2e-local-prod-tanstack-start-	128	0	26
✅ e2e-vercel-prod-nest	126	0	28
✅ e2e-vercel-prod-tanstack-start	126	0	28

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

---

📋 View full workflow run

[github-actions]

📊 Workflow Benchmarks

commit 164e7d3 · Wed, 29 Jul 2026 06:36:12 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	424 (-39%) 💚	1299 🔴 (+26%) 🔻	1315 🔴 (+24%) 🔻	1415 🔴 (-15%)	30
TTFS	stream	1251 (+30%) 🔻	1316 🔴 (+29%) 🔻	1330 🔴 (+28%) 🔻	1428 🔴 (+23%) 🔻	30
TTFS	hook + stream	1482 (+26%) 🔻	1532 🔴 (+18%) 🔻	1597 🔴 (+17%) 🔻	1953 🔴 (+27%) 🔻	30
STSO	1020 steps (1-20)	166 (-8.8%)	254 🔴 (-3.4%)	290 🔴 (-11%)	313 🔴 (-17%) 💚	19
STSO	1020 steps (101-120)	186 (-2.6%)	241 🔴 (-8.0%)	270 🔴 (-18%) 💚	378 🔴 (-64%) 💚	19
STSO	1020 steps (1001-1020)	477 (+1.5%)	583 🔴 (+4.1%)	676 🔴 (-3.3%)	717 🔴 (-6.6%)	19
WO	1020 steps	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	1
SL	stream latency	96 (+22%) 🔻	142 🔴 (+12%)	162 🔴 (+3.8%)	181 🔴 (-18%) 💚	30
SO	stream overhead (text)	95 (-13%)	210 (±0%)	350 (+10%)	3151 🔴 (+399%) 🔻	30
SO	stream overhead (structured)	98 (-2.0%)	144 (-17%) 💚	160 (-18%) 💚	240 (-43%) 💚	30

📜 Previous results (1)

003f800

Mon, 27 Jul 2026 22:42:23 GMT · run logs

vercel / nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	238 (-68%) 💚	1374 🔴 (+21%) 🔻	1408 🔴 (+16%) 🔻	1708 🔴 (+25%) 🔻	30
TTFS	stream	242 (-23%) 💚	1347 🔴 (+23%) 🔻	1384 🔴 (+21%) 🔻	1396 🔴 (+19%) 🔻	30
TTFS	hook + stream	400 (-68%) 💚	1555 🔴 (+11%)	1601 🔴 (+9.6%)	1624 🔴 (-0.7%)	30
STSO	1020 steps (1-20)	167 (-1.8%)	273 🔴 (-9.6%)	283 🔴 (-20%) 💚	347 🔴 (-8.4%)	19
STSO	1020 steps (101-120)	206 (+4.6%)	302 🔴 (-11%)	477 🔴 (+17%) 🔻	2242 🔴 (+348%) 🔻	19
STSO	1020 steps (1001-1020)	472 (-2.3%)	551 🔴 (-4.0%)	591 🔴 (-8.5%)	1103 🔴 (+68%) 🔻	19
WO	1020 steps	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	1
SL	stream latency	101 (+8.6%)	148 🔴 (-12%)	179 🔴 (-24%) 💚	250 🔴 (-1.2%)	30
SO	stream overhead (text)	115 (-12%)	185 (-36%) 💚	209 (-41%) 💚	401 (-4.8%)	30
SO	stream overhead (structured)	124 (-8.1%)	209 (-20%) 💚	256 (-7.9%)	430 (+4.1%)	30

ℹ️ Metric definitions & methodology

_{Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.}

_{Metrics — TTFS: time to first step body (in-deployment start() → first step body, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)}

_{Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost}

_{🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120}

_{All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.}

_{Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.}

[github-actions]

No backport to stable for a09d001 (AI decision).

This commit reverts #2752 (static world-target injection), which only ever landed on main — origin/stable has no packages/core/src/runtime/world-target.ts, no packages/builders/src/world-target.ts, no packages/core/vitest.config.ts world-target alias, and its packages/core/src/runtime/world.ts / packages/utils/src/world-target.ts already resolve the world at runtime from WORKFLOW_TARGET_WORLD, i.e. exactly the behavior this revert restores. Backporting a revert of something absent from stable would only churn unrelated files (nitro/next/sveltekit builder changes, workbench configs, v5 docs) with no corresponding defect fix.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

a09d00135bd96f22bd1ae1dee6b5a6f797b7d804

[VaguelySerious]

Reverts #2752 ("Statically inject workflow world target"). The world package is once again resolved at runtime from WORKFLOW_TARGET_WORLD instead of being aliased into host bundles at build time.

Why this is a surgical revert

141 commits have landed on top of #2752, several of which build on it, so git revert alone leaves the tree unbuildable. This branch removes the static-injection mechanism and restores the pre-#2752 runtime resolution while keeping everything that landed after it.

Removed

• world-target modules in @workflow/core, @workflow/builders, and the Statically inject workflow world target #2752 additions to @workflow/utils
• the bundler aliases / defines wired through next, nitro, nuxt, astro, sveltekit, rollup, and both nest builders
• the @workflow/core/runtime/world-target export, its tsconfig/vitest path aliases
• the pg-native stub alias and the extracted node-compat banner constants, which only existed because the world package was forced into the SSR bundle (the sveltekit typescript stub alias from fix(sveltekit): production server crash from bundled TypeScript compiler #2799 goes with them for the same reason)

Kept

• createWorldFromModule / WorldFactoryModule in core — still used by @workflow/world-testing and the nitro dev virtual handler
• world-init / world-init-stub / getWorldLazy and the globalThis[GetWorldFnKey] ??= getWorld registration, plus the test: regression coverage for hook.resume() from isolated route bundles (o2flow beta.26 incident) #3001 isolated-route-bundle regression test
• web: construct worlds explicitly instead of via static-injection stub #2804 (web), cli: restore dynamic world loading for community backends #2806 (cli dynamic community backends), Remove obsolete world factory aliases #3112 (world factory alias removal — core now imports createWorld from the world packages), [nest] Fix NestJS Vercel build output #2988 (nest vercel builder), Fix duplicate transforms of Nitro build artifacts #2925 / Fix Nitro cleanup for React Router and add setup guides #2908 (nitro), next basePath support, windows/canary test-timeout tuning

Note on the o2flow incident that motivated #2752

The o2flow failure (Cannot find module as expression is too dynamic on sandboxDoneHook.resume()) was caused by the world registration being tree-shaken out of an isolated route bundle, which made getWorldLazy() fall through to an obfuscated import() that Turbopack stubs. That path is fixed by the world-init side-effect import on every host entrypoint plus the loud "world runtime was not initialized" error — both of which this revert keeps, along with #3001's regression test. o2flow runs on the Vercel world, which core imports statically, so it never reaches the dynamic resolution path this revert restores.

A follow-up PR stacked on this one proposes hardening the remaining dynamic path (custom world packages under Turbopack/webpack) without reintroducing build-time injection.

Verification

• pnpm build, pnpm typecheck green
• unit tests for the affected packages green

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-nextjs-workflow-webpack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-astro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-express-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-fastify-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-hono-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nestjs-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nitro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nuxt-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-sveltekit-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-tanstack-start-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-vite-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-docs	Ready	Preview, Comment, Open in v0	Jul 29, 2026 6:18am
workflow-swc-playground	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-tarballs	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-web	Ready	Preview, Comment	Jul 29, 2026 6:18am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 164e7d3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 21 packages

Name	Type
@workflow/builders	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/nuxt	Patch
@workflow/astro	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/utils	Patch
@workflow/cli	Patch
@workflow/world-testing	Patch
@workflow/world-local	Patch
@workflow/world-vercel	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/vitest	Patch
@workflow/web-shared	Patch
@workflow/web	Patch
@workflow/errors	Patch
@workflow/world-postgres	Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

🧪 E2E Test Results

✅ All tests passed

E2E Test Summary

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	1455	0	239	1694
✅ 💻 Local Development	1621	0	227	1848
✅ 📦 Local Production	1621	0	227	1848
✅ 🐘 Local Postgres	1621	0	227	1848
✅ 🪟 Windows	154	0	0	154
✅ 📋 Other	1020	0	212	1232
✅ vercel-multi-region	27	0	0	27
Total	7519	0	1132	8651

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	126	0	28
✅ example	126	0	28
✅ express	126	0	28
✅ fastify	126	0	28
✅ hono	126	0	28
✅ nextjs-turbopack	151	0	3
✅ nextjs-webpack	151	0	3
✅ nitro	126	0	28
✅ nuxt	126	0	28
✅ sveltekit	145	0	9
✅ vite	126	0	28

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	154	0	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	128	0	26
✅ e2e-local-dev-tanstack-start-	128	0	26
✅ e2e-local-postgres-nest-stable	128	0	26
✅ e2e-local-postgres-tanstack-start-	128	0	26
✅ e2e-local-prod-nest-stable	128	0	26
✅ e2e-local-prod-tanstack-start-	128	0	26
✅ e2e-vercel-prod-nest	126	0	28
✅ e2e-vercel-prod-tanstack-start	126	0	28

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

---

📋 View full workflow run

[github-actions]

📊 Workflow Benchmarks

commit 164e7d3 · Wed, 29 Jul 2026 06:36:12 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	424 (-39%) 💚	1299 🔴 (+26%) 🔻	1315 🔴 (+24%) 🔻	1415 🔴 (-15%)	30
TTFS	stream	1251 (+30%) 🔻	1316 🔴 (+29%) 🔻	1330 🔴 (+28%) 🔻	1428 🔴 (+23%) 🔻	30
TTFS	hook + stream	1482 (+26%) 🔻	1532 🔴 (+18%) 🔻	1597 🔴 (+17%) 🔻	1953 🔴 (+27%) 🔻	30
STSO	1020 steps (1-20)	166 (-8.8%)	254 🔴 (-3.4%)	290 🔴 (-11%)	313 🔴 (-17%) 💚	19
STSO	1020 steps (101-120)	186 (-2.6%)	241 🔴 (-8.0%)	270 🔴 (-18%) 💚	378 🔴 (-64%) 💚	19
STSO	1020 steps (1001-1020)	477 (+1.5%)	583 🔴 (+4.1%)	676 🔴 (-3.3%)	717 🔴 (-6.6%)	19
WO	1020 steps	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	1
SL	stream latency	96 (+22%) 🔻	142 🔴 (+12%)	162 🔴 (+3.8%)	181 🔴 (-18%) 💚	30
SO	stream overhead (text)	95 (-13%)	210 (±0%)	350 (+10%)	3151 🔴 (+399%) 🔻	30
SO	stream overhead (structured)	98 (-2.0%)	144 (-17%) 💚	160 (-18%) 💚	240 (-43%) 💚	30

📜 Previous results (1)

003f800

Mon, 27 Jul 2026 22:42:23 GMT · run logs

vercel / nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	238 (-68%) 💚	1374 🔴 (+21%) 🔻	1408 🔴 (+16%) 🔻	1708 🔴 (+25%) 🔻	30
TTFS	stream	242 (-23%) 💚	1347 🔴 (+23%) 🔻	1384 🔴 (+21%) 🔻	1396 🔴 (+19%) 🔻	30
TTFS	hook + stream	400 (-68%) 💚	1555 🔴 (+11%)	1601 🔴 (+9.6%)	1624 🔴 (-0.7%)	30
STSO	1020 steps (1-20)	167 (-1.8%)	273 🔴 (-9.6%)	283 🔴 (-20%) 💚	347 🔴 (-8.4%)	19
STSO	1020 steps (101-120)	206 (+4.6%)	302 🔴 (-11%)	477 🔴 (+17%) 🔻	2242 🔴 (+348%) 🔻	19
STSO	1020 steps (1001-1020)	472 (-2.3%)	551 🔴 (-4.0%)	591 🔴 (-8.5%)	1103 🔴 (+68%) 🔻	19
WO	1020 steps	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	1
SL	stream latency	101 (+8.6%)	148 🔴 (-12%)	179 🔴 (-24%) 💚	250 🔴 (-1.2%)	30
SO	stream overhead (text)	115 (-12%)	185 (-36%) 💚	209 (-41%) 💚	401 (-4.8%)	30
SO	stream overhead (structured)	124 (-8.1%)	209 (-20%) 💚	256 (-7.9%)	430 (+4.1%)	30

ℹ️ Metric definitions & methodology

_{Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.}

_{Metrics — TTFS: time to first step body (in-deployment start() → first step body, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)}

_{Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost}

_{🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120}

_{All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.}

_{Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.}

[github-actions]

No backport to stable for a09d001 (AI decision).

This commit reverts #2752 (static world-target injection), which only ever landed on main — origin/stable has no packages/core/src/runtime/world-target.ts, no packages/builders/src/world-target.ts, no packages/core/vitest.config.ts world-target alias, and its packages/core/src/runtime/world.ts / packages/utils/src/world-target.ts already resolve the world at runtime from WORKFLOW_TARGET_WORLD, i.e. exactly the behavior this revert restores. Backporting a revert of something absent from stable would only churn unrelated files (nitro/next/sveltekit builder changes, workbench configs, v5 docs) with no corresponding defect fix.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

a09d00135bd96f22bd1ae1dee6b5a6f797b7d804

[VaguelySerious]

Reverts #2752 ("Statically inject workflow world target"). The world package is once again resolved at runtime from WORKFLOW_TARGET_WORLD instead of being aliased into host bundles at build time.

Why this is a surgical revert

141 commits have landed on top of #2752, several of which build on it, so git revert alone leaves the tree unbuildable. This branch removes the static-injection mechanism and restores the pre-#2752 runtime resolution while keeping everything that landed after it.

Removed

• world-target modules in @workflow/core, @workflow/builders, and the Statically inject workflow world target #2752 additions to @workflow/utils
• the bundler aliases / defines wired through next, nitro, nuxt, astro, sveltekit, rollup, and both nest builders
• the @workflow/core/runtime/world-target export, its tsconfig/vitest path aliases
• the pg-native stub alias and the extracted node-compat banner constants, which only existed because the world package was forced into the SSR bundle (the sveltekit typescript stub alias from fix(sveltekit): production server crash from bundled TypeScript compiler #2799 goes with them for the same reason)

Kept

• createWorldFromModule / WorldFactoryModule in core — still used by @workflow/world-testing and the nitro dev virtual handler
• world-init / world-init-stub / getWorldLazy and the globalThis[GetWorldFnKey] ??= getWorld registration, plus the test: regression coverage for hook.resume() from isolated route bundles (o2flow beta.26 incident) #3001 isolated-route-bundle regression test
• web: construct worlds explicitly instead of via static-injection stub #2804 (web), cli: restore dynamic world loading for community backends #2806 (cli dynamic community backends), Remove obsolete world factory aliases #3112 (world factory alias removal — core now imports createWorld from the world packages), [nest] Fix NestJS Vercel build output #2988 (nest vercel builder), Fix duplicate transforms of Nitro build artifacts #2925 / Fix Nitro cleanup for React Router and add setup guides #2908 (nitro), next basePath support, windows/canary test-timeout tuning

Note on the o2flow incident that motivated #2752

The o2flow failure (Cannot find module as expression is too dynamic on sandboxDoneHook.resume()) was caused by the world registration being tree-shaken out of an isolated route bundle, which made getWorldLazy() fall through to an obfuscated import() that Turbopack stubs. That path is fixed by the world-init side-effect import on every host entrypoint plus the loud "world runtime was not initialized" error — both of which this revert keeps, along with #3001's regression test. o2flow runs on the Vercel world, which core imports statically, so it never reaches the dynamic resolution path this revert restores.

A follow-up PR stacked on this one proposes hardening the remaining dynamic path (custom world packages under Turbopack/webpack) without reintroducing build-time injection.

Verification

• pnpm build, pnpm typecheck green
• unit tests for the affected packages green

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-nextjs-workflow-webpack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-astro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-express-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-fastify-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-hono-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nestjs-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nitro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nuxt-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-sveltekit-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-tanstack-start-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-vite-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-docs	Ready	Preview, Comment, Open in v0	Jul 29, 2026 6:18am
workflow-swc-playground	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-tarballs	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-web	Ready	Preview, Comment	Jul 29, 2026 6:18am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 164e7d3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 21 packages

Name	Type
@workflow/builders	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/nuxt	Patch
@workflow/astro	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/utils	Patch
@workflow/cli	Patch
@workflow/world-testing	Patch
@workflow/world-local	Patch
@workflow/world-vercel	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/vitest	Patch
@workflow/web-shared	Patch
@workflow/web	Patch
@workflow/errors	Patch
@workflow/world-postgres	Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

🧪 E2E Test Results

✅ All tests passed

E2E Test Summary

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	1455	0	239	1694
✅ 💻 Local Development	1621	0	227	1848
✅ 📦 Local Production	1621	0	227	1848
✅ 🐘 Local Postgres	1621	0	227	1848
✅ 🪟 Windows	154	0	0	154
✅ 📋 Other	1020	0	212	1232
✅ vercel-multi-region	27	0	0	27
Total	7519	0	1132	8651

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	126	0	28
✅ example	126	0	28
✅ express	126	0	28
✅ fastify	126	0	28
✅ hono	126	0	28
✅ nextjs-turbopack	151	0	3
✅ nextjs-webpack	151	0	3
✅ nitro	126	0	28
✅ nuxt	126	0	28
✅ sveltekit	145	0	9
✅ vite	126	0	28

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	154	0	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	128	0	26
✅ e2e-local-dev-tanstack-start-	128	0	26
✅ e2e-local-postgres-nest-stable	128	0	26
✅ e2e-local-postgres-tanstack-start-	128	0	26
✅ e2e-local-prod-nest-stable	128	0	26
✅ e2e-local-prod-tanstack-start-	128	0	26
✅ e2e-vercel-prod-nest	126	0	28
✅ e2e-vercel-prod-tanstack-start	126	0	28

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

---

📋 View full workflow run

[github-actions]

📊 Workflow Benchmarks

commit 164e7d3 · Wed, 29 Jul 2026 06:36:12 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	424 (-39%) 💚	1299 🔴 (+26%) 🔻	1315 🔴 (+24%) 🔻	1415 🔴 (-15%)	30
TTFS	stream	1251 (+30%) 🔻	1316 🔴 (+29%) 🔻	1330 🔴 (+28%) 🔻	1428 🔴 (+23%) 🔻	30
TTFS	hook + stream	1482 (+26%) 🔻	1532 🔴 (+18%) 🔻	1597 🔴 (+17%) 🔻	1953 🔴 (+27%) 🔻	30
STSO	1020 steps (1-20)	166 (-8.8%)	254 🔴 (-3.4%)	290 🔴 (-11%)	313 🔴 (-17%) 💚	19
STSO	1020 steps (101-120)	186 (-2.6%)	241 🔴 (-8.0%)	270 🔴 (-18%) 💚	378 🔴 (-64%) 💚	19
STSO	1020 steps (1001-1020)	477 (+1.5%)	583 🔴 (+4.1%)	676 🔴 (-3.3%)	717 🔴 (-6.6%)	19
WO	1020 steps	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	1
SL	stream latency	96 (+22%) 🔻	142 🔴 (+12%)	162 🔴 (+3.8%)	181 🔴 (-18%) 💚	30
SO	stream overhead (text)	95 (-13%)	210 (±0%)	350 (+10%)	3151 🔴 (+399%) 🔻	30
SO	stream overhead (structured)	98 (-2.0%)	144 (-17%) 💚	160 (-18%) 💚	240 (-43%) 💚	30

📜 Previous results (1)

003f800

Mon, 27 Jul 2026 22:42:23 GMT · run logs

vercel / nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	238 (-68%) 💚	1374 🔴 (+21%) 🔻	1408 🔴 (+16%) 🔻	1708 🔴 (+25%) 🔻	30
TTFS	stream	242 (-23%) 💚	1347 🔴 (+23%) 🔻	1384 🔴 (+21%) 🔻	1396 🔴 (+19%) 🔻	30
TTFS	hook + stream	400 (-68%) 💚	1555 🔴 (+11%)	1601 🔴 (+9.6%)	1624 🔴 (-0.7%)	30
STSO	1020 steps (1-20)	167 (-1.8%)	273 🔴 (-9.6%)	283 🔴 (-20%) 💚	347 🔴 (-8.4%)	19
STSO	1020 steps (101-120)	206 (+4.6%)	302 🔴 (-11%)	477 🔴 (+17%) 🔻	2242 🔴 (+348%) 🔻	19
STSO	1020 steps (1001-1020)	472 (-2.3%)	551 🔴 (-4.0%)	591 🔴 (-8.5%)	1103 🔴 (+68%) 🔻	19
WO	1020 steps	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	1
SL	stream latency	101 (+8.6%)	148 🔴 (-12%)	179 🔴 (-24%) 💚	250 🔴 (-1.2%)	30
SO	stream overhead (text)	115 (-12%)	185 (-36%) 💚	209 (-41%) 💚	401 (-4.8%)	30
SO	stream overhead (structured)	124 (-8.1%)	209 (-20%) 💚	256 (-7.9%)	430 (+4.1%)	30

ℹ️ Metric definitions & methodology

_{Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.}

_{Metrics — TTFS: time to first step body (in-deployment start() → first step body, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)}

_{Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost}

_{🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120}

_{All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.}

_{Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.}

[github-actions]

No backport to stable for a09d001 (AI decision).

This commit reverts #2752 (static world-target injection), which only ever landed on main — origin/stable has no packages/core/src/runtime/world-target.ts, no packages/builders/src/world-target.ts, no packages/core/vitest.config.ts world-target alias, and its packages/core/src/runtime/world.ts / packages/utils/src/world-target.ts already resolve the world at runtime from WORKFLOW_TARGET_WORLD, i.e. exactly the behavior this revert restores. Backporting a revert of something absent from stable would only churn unrelated files (nitro/next/sveltekit builder changes, workbench configs, v5 docs) with no corresponding defect fix.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

a09d00135bd96f22bd1ae1dee6b5a6f797b7d804

[VaguelySerious]

Reverts #2752 ("Statically inject workflow world target"). The world package is once again resolved at runtime from WORKFLOW_TARGET_WORLD instead of being aliased into host bundles at build time.

Why this is a surgical revert

141 commits have landed on top of #2752, several of which build on it, so git revert alone leaves the tree unbuildable. This branch removes the static-injection mechanism and restores the pre-#2752 runtime resolution while keeping everything that landed after it.

Removed

• world-target modules in @workflow/core, @workflow/builders, and the Statically inject workflow world target #2752 additions to @workflow/utils
• the bundler aliases / defines wired through next, nitro, nuxt, astro, sveltekit, rollup, and both nest builders
• the @workflow/core/runtime/world-target export, its tsconfig/vitest path aliases
• the pg-native stub alias and the extracted node-compat banner constants, which only existed because the world package was forced into the SSR bundle (the sveltekit typescript stub alias from fix(sveltekit): production server crash from bundled TypeScript compiler #2799 goes with them for the same reason)

Kept

• createWorldFromModule / WorldFactoryModule in core — still used by @workflow/world-testing and the nitro dev virtual handler
• world-init / world-init-stub / getWorldLazy and the globalThis[GetWorldFnKey] ??= getWorld registration, plus the test: regression coverage for hook.resume() from isolated route bundles (o2flow beta.26 incident) #3001 isolated-route-bundle regression test
• web: construct worlds explicitly instead of via static-injection stub #2804 (web), cli: restore dynamic world loading for community backends #2806 (cli dynamic community backends), Remove obsolete world factory aliases #3112 (world factory alias removal — core now imports createWorld from the world packages), [nest] Fix NestJS Vercel build output #2988 (nest vercel builder), Fix duplicate transforms of Nitro build artifacts #2925 / Fix Nitro cleanup for React Router and add setup guides #2908 (nitro), next basePath support, windows/canary test-timeout tuning

Note on the o2flow incident that motivated #2752

The o2flow failure (Cannot find module as expression is too dynamic on sandboxDoneHook.resume()) was caused by the world registration being tree-shaken out of an isolated route bundle, which made getWorldLazy() fall through to an obfuscated import() that Turbopack stubs. That path is fixed by the world-init side-effect import on every host entrypoint plus the loud "world runtime was not initialized" error — both of which this revert keeps, along with #3001's regression test. o2flow runs on the Vercel world, which core imports statically, so it never reaches the dynamic resolution path this revert restores.

A follow-up PR stacked on this one proposes hardening the remaining dynamic path (custom world packages under Turbopack/webpack) without reintroducing build-time injection.

Verification

• pnpm build, pnpm typecheck green
• unit tests for the affected packages green

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-nextjs-workflow-webpack	Ready	Preview, Comment	Jul 29, 2026 6:18am
example-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-astro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-express-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-fastify-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-hono-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nestjs-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nitro-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-nuxt-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-sveltekit-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-tanstack-start-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workbench-vite-workflow	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-docs	Ready	Preview, Comment, Open in v0	Jul 29, 2026 6:18am
workflow-swc-playground	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-tarballs	Ready	Preview, Comment	Jul 29, 2026 6:18am
workflow-web	Ready	Preview, Comment	Jul 29, 2026 6:18am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 164e7d3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 21 packages

Name	Type
@workflow/builders	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/nuxt	Patch
@workflow/astro	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/utils	Patch
@workflow/cli	Patch
@workflow/world-testing	Patch
@workflow/world-local	Patch
@workflow/world-vercel	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/vitest	Patch
@workflow/web-shared	Patch
@workflow/web	Patch
@workflow/errors	Patch
@workflow/world-postgres	Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

🧪 E2E Test Results

✅ All tests passed

E2E Test Summary

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	1455	0	239	1694
✅ 💻 Local Development	1621	0	227	1848
✅ 📦 Local Production	1621	0	227	1848
✅ 🐘 Local Postgres	1621	0	227	1848
✅ 🪟 Windows	154	0	0	154
✅ 📋 Other	1020	0	212	1232
✅ vercel-multi-region	27	0	0	27
Total	7519	0	1132	8651

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	126	0	28
✅ example	126	0	28
✅ express	126	0	28
✅ fastify	126	0	28
✅ hono	126	0	28
✅ nextjs-turbopack	151	0	3
✅ nextjs-webpack	151	0	3
✅ nitro	126	0	28
✅ nuxt	126	0	28
✅ sveltekit	145	0	9
✅ vite	126	0	28

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	128	0	26
✅ express-stable	128	0	26
✅ fastify-stable	128	0	26
✅ hono-stable	128	0	26
✅ nextjs-turbopack-canary	135	0	19
✅ nextjs-turbopack-stable	154	0	0
✅ nextjs-webpack-canary	135	0	19
✅ nextjs-webpack-stable	154	0	0
✅ nitro-stable	128	0	26
✅ nuxt-stable	128	0	26
✅ sveltekit-stable	147	0	7
✅ vite-stable	128	0	26

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	154	0	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	128	0	26
✅ e2e-local-dev-tanstack-start-	128	0	26
✅ e2e-local-postgres-nest-stable	128	0	26
✅ e2e-local-postgres-tanstack-start-	128	0	26
✅ e2e-local-prod-nest-stable	128	0	26
✅ e2e-local-prod-tanstack-start-	128	0	26
✅ e2e-vercel-prod-nest	126	0	28
✅ e2e-vercel-prod-tanstack-start	126	0	28

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

---

📋 View full workflow run

[github-actions]

📊 Workflow Benchmarks

commit 164e7d3 · Wed, 29 Jul 2026 06:36:12 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	424 (-39%) 💚	1299 🔴 (+26%) 🔻	1315 🔴 (+24%) 🔻	1415 🔴 (-15%)	30
TTFS	stream	1251 (+30%) 🔻	1316 🔴 (+29%) 🔻	1330 🔴 (+28%) 🔻	1428 🔴 (+23%) 🔻	30
TTFS	hook + stream	1482 (+26%) 🔻	1532 🔴 (+18%) 🔻	1597 🔴 (+17%) 🔻	1953 🔴 (+27%) 🔻	30
STSO	1020 steps (1-20)	166 (-8.8%)	254 🔴 (-3.4%)	290 🔴 (-11%)	313 🔴 (-17%) 💚	19
STSO	1020 steps (101-120)	186 (-2.6%)	241 🔴 (-8.0%)	270 🔴 (-18%) 💚	378 🔴 (-64%) 💚	19
STSO	1020 steps (1001-1020)	477 (+1.5%)	583 🔴 (+4.1%)	676 🔴 (-3.3%)	717 🔴 (-6.6%)	19
WO	1020 steps	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	380460 (-6.0%)	1
SL	stream latency	96 (+22%) 🔻	142 🔴 (+12%)	162 🔴 (+3.8%)	181 🔴 (-18%) 💚	30
SO	stream overhead (text)	95 (-13%)	210 (±0%)	350 (+10%)	3151 🔴 (+399%) 🔻	30
SO	stream overhead (structured)	98 (-2.0%)	144 (-17%) 💚	160 (-18%) 💚	240 (-43%) 💚	30

📜 Previous results (1)

003f800

Mon, 27 Jul 2026 22:42:23 GMT · run logs

vercel / nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	238 (-68%) 💚	1374 🔴 (+21%) 🔻	1408 🔴 (+16%) 🔻	1708 🔴 (+25%) 🔻	30
TTFS	stream	242 (-23%) 💚	1347 🔴 (+23%) 🔻	1384 🔴 (+21%) 🔻	1396 🔴 (+19%) 🔻	30
TTFS	hook + stream	400 (-68%) 💚	1555 🔴 (+11%)	1601 🔴 (+9.6%)	1624 🔴 (-0.7%)	30
STSO	1020 steps (1-20)	167 (-1.8%)	273 🔴 (-9.6%)	283 🔴 (-20%) 💚	347 🔴 (-8.4%)	19
STSO	1020 steps (101-120)	206 (+4.6%)	302 🔴 (-11%)	477 🔴 (+17%) 🔻	2242 🔴 (+348%) 🔻	19
STSO	1020 steps (1001-1020)	472 (-2.3%)	551 🔴 (-4.0%)	591 🔴 (-8.5%)	1103 🔴 (+68%) 🔻	19
WO	1020 steps	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	411119 (-6.4%)	1
SL	stream latency	101 (+8.6%)	148 🔴 (-12%)	179 🔴 (-24%) 💚	250 🔴 (-1.2%)	30
SO	stream overhead (text)	115 (-12%)	185 (-36%) 💚	209 (-41%) 💚	401 (-4.8%)	30
SO	stream overhead (structured)	124 (-8.1%)	209 (-20%) 💚	256 (-7.9%)	430 (+4.1%)	30

ℹ️ Metric definitions & methodology

_{Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.}

_{Metrics — TTFS: time to first step body (in-deployment start() → first step body, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)}

_{Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost}

_{🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120}

_{All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.}

_{Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.}

[github-actions]

No backport to stable for a09d001 (AI decision).

This commit reverts #2752 (static world-target injection), which only ever landed on main — origin/stable has no packages/core/src/runtime/world-target.ts, no packages/builders/src/world-target.ts, no packages/core/vitest.config.ts world-target alias, and its packages/core/src/runtime/world.ts / packages/utils/src/world-target.ts already resolve the world at runtime from WORKFLOW_TARGET_WORLD, i.e. exactly the behavior this revert restores. Backporting a revert of something absent from stable would only churn unrelated files (nitro/next/sveltekit builder changes, workbench configs, v5 docs) with no corresponding defect fix.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

a09d00135bd96f22bd1ae1dee6b5a6f797b7d804