[4/4] Move workbench code-block styles to Tailwind

[mitul-s]

Description

• Replace the static content-visibility and intrinsic-size inline styles on workbench code blocks with Tailwind arbitrary-property utilities.
• Preserve consumer-provided style overrides.

Stack

1. Shared UI components
2. Trace viewer
3. Workflow web/graph
4. This PR — workbench code block

Merge in order from 1 to 4.

How did you test your changes?

• Biome check on the changed component — no errors
• A recursive workbench build was blocked by the VM's Cargo 1.83 lacking edition2024 support for @workflow/swc-plugin.
• A direct workbench build was consequently blocked by the unavailable generated workflow/dist/next.cjs dependency.

PR Checklist - Required to merge

• 📦 pnpm changeset --empty was run for this workbench-only PR
• 🔒 DCO sign-off passes (git commit --signoff)
• 📝 Ping @vercel/workflow in a comment once the PR is ready, and the above checklist is complete

  

[changeset-bot]

🦋 Changeset detected

Latest commit: b5e18c8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 16 packages

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

Not sure what this means? Click here to learn what changesets are.

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

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview	Aug 3, 2026 9:01pm
example-nextjs-workflow-webpack	Ready	Preview	Aug 3, 2026 9:01pm
example-workflow	Ready	Preview	Aug 3, 2026 9:01pm
workbench-astro-workflow	Ready	Preview	Aug 3, 2026 9:01pm
workbench-express-workflow	Ready	Preview	Aug 3, 2026 9:01pm
workbench-fastify-workflow	Ready	Preview	Aug 3, 2026 9:01pm
workbench-hono-workflow	Ready	Preview	Aug 3, 2026 9:01pm
workbench-nestjs-workflow	Ready	Preview	Aug 3, 2026 9:01pm
workbench-nitro-workflow	Ready	Preview	Aug 3, 2026 9:01pm
workbench-nuxt-workflow	Ready	Preview	Aug 3, 2026 9:01pm
workbench-sveltekit-workflow	Ready	Preview	Aug 3, 2026 9:01pm
workbench-tanstack-start-workflow	Ready	Preview	Aug 3, 2026 9:01pm
workbench-vite-workflow	Ready	Preview	Aug 3, 2026 9:01pm
workflow-docs	Ready	Preview, v0	Aug 3, 2026 9:01pm
workflow-swc-playground	Ready	Preview	Aug 3, 2026 9:01pm
workflow-tarballs	Ready	Preview	Aug 3, 2026 9:01pm
workflow-web	Ready	Preview	Aug 3, 2026 9:01pm

[github-actions]

🧪 E2E Test Results

❌ Some tests failed

❌ Failed E2E Tests

▲ Vercel Production (2 failed)

nextjs-turbopack (1 failed):

• pages router sleepingWorkflow via pages router

vite (1 failed):

• fibonacciWorkflow - recursive workflow composition via start() | wrun_41KZ4QC80A0GTAHZ13JJ3DWF5M | 🔍 observability

💻 Local Development (1 failed)

sveltekit-stable (1 failed):

• webhookWorkflow | wrun_41KZ4PYJD80GR5KZ0JDZRHQHXB

📋 Other (1 failed)

e2e-local-prod-nest-stable (1 failed):

• webhookWorkflow | wrun_41KZ4PYJD80GR5KZ0JDZRHQHXB

vercel-multi-region (1 failed)

nextjs-turbopack (1 failed):

• multi-region (world-vercel) implicit region: region-pinned routes without a region option /api/e2e-region-implicit/fra1 mints a run tagged with its VERCEL_REGION

E2E Test Summary

Summary

	Passed	Failed	Skipped	Total
❌ ▲ Vercel Production	1453	2	239	1694
❌ 💻 Local Development	1620	1	227	1848
✅ 📦 Local Production	1621	0	227	1848
✅ 🐘 Local Postgres	1621	0	227	1848
✅ 🪟 Windows	154	0	0	154
❌ 📋 Other	1019	1	212	1232
❌ vercel-multi-region	26	1	0	27
Total	7514	5	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	150	1	3
✅ nextjs-webpack	151	0	3
✅ nitro	126	0	28
✅ nuxt	126	0	28
✅ sveltekit	145	0	9
❌ vite	125	1	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	146	1	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	127	1	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	26	1	0

---

📋 View full workflow run

[github-actions]

📊 Workflow Benchmarks

commit b5e18c8 · Mon, 03 Aug 2026 21:22:26 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	1302 (+575%) 🔻	1455 🔴 (+43%) 🔻	1523 🔴 (+44%) 🔻	1827 🔴 (+44%) 🔻	30
TTFS	stream	1306 (+507%) 🔻	1373 🔴 (+31%) 🔻	1394 🔴 (+32%) 🔻	1470 🔴 (±0%)	30
TTFS	hook + stream	1415 (+268%) 🔻	1801 🔴 (+44%) 🔻	1898 🔴 (+48%) 🔻	2072 🔴 (+47%) 🔻	30
STSO	1020 steps (inline)	193 (+10%)	494 (±0%)	569 (+3.6%)	741 (-40%) 💚	1016
STSO	1020 steps (queue-hop)	2480 (+56%) 🔻	3298 (-89%) 💚	3298 (-97%) 💚	3298 (-97%) 💚	3
WO	1020 steps	438253 (-49%) 💚	438253 (-49%) 💚	438253 (-49%) 💚	438253 (-49%) 💚	1
SL	stream latency	133 (+55%) 🔻	198 🔴 (+20%) 🔻	209 🔴 (+6.6%)	372 🔴 (+14%)	30
SO	stream overhead (text)	142 (+11%)	197 (-95%) 💚	207 (-99%) 💚	232 (-100%) 💚	30
SO	stream overhead (structured)	146 (+6.6%)	217 (-50%) 💚	241 (-98%) 💚	459 (-99%) 💚	30

📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 695511ms → this run 427879ms (Δ -267632ms, -38%)

      150-200 ms  ┃                         main   6  this   1    -5
      200-250 ms  ████████┃                 main  56  this  66   +10
      250-300 ms  ███████████████░┃         main 106  this 123   +17
      300-350 ms  ██████████████████┃█      main 145  this 139    -6
      350-400 ms  ███████████████┃████      main 141  this 112   -29
      400-450 ms  ██████████████████████░┃  main 161  this 172   +11
      450-500 ms  █████████████████████┃    main 155  this 161    +6
      500-550 ms  ███████████████┃████      main 142  this 112   -30
      550-600 ms  ███████░┃                 main  47  this  62   +15
      600-650 ms  ███░┃                     main  18  this  38   +20
      650-700 ms  █┃                        main   7  this  12    +5
      700-750 ms  ┃                         main   8  this   9    +1
      750-800 ms  ┃                         main   3  this   2    -1
      800-850 ms  ┃                         main   4  this   3    -1
      900-950 ms  ┃                         main   1  this   1    +0
    1000-1050 ms  ┃                         main   1  this   0    -1
    1050-1100 ms  ┃                         main   0  this   1    +1
    1150-1200 ms  ┃                         main   1  this   1    +0
    1200-1250 ms  ┃                         main   1  this   0    -1
    1250-1300 ms  ┃                         main   1  this   0    -1
    1900-1950 ms  ┃                         main   0  this   1    +1
    4000-4050 ms  ┃                         main   1  this   0    -1
    8600-8650 ms  ┃                         main   1  this   0    -1
    9850-9900 ms  ┃                         main   1  this   0    -1
  12450-12500 ms  ┃                         main   1  this   0    -1
  15900-15950 ms  ┃                         main   1  this   0    -1
  35150-35200 ms  ┃                         main   1  this   0    -1
  35200-35250 ms  ┃                         main   1  this   0    -1
  48400-48450 ms  ┃                         main   1  this   0    -1
106950-107000 ms  ┃                         main   1  this   0    -1

1020 steps (queue-hop)

Cumulative STSO time: main 161965ms → this run 9062ms (Δ -152903ms, -94%)

      0-20000 ms  █████████████████┃██████  main 4  this 3  -1
  20000-40000 ms  ┃█████                    main 1  this 0  -1
120000-140000 ms  ┃█████                    main 1  this 0  -1

ℹ️ Metric definitions & methodology

_{The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: █ is main, ┃ marks where this run lands, ░ bridges the gap when this run has more samples in a bucket.}

_{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}

_{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.}