test(e2e): expect a takeover when the World raises a force-claim victim to its executor's spec version by pranaygp · Pull Request #4462 · vercel/workflow

pranaygp · 2026-09-28T20:58:18Z

Problem

createHook({ experimental_force: true }) > declines to take a token from a run whose runtime predates involuntary disposal times out (90s, then again on retry) on essentially every Vercel E2E lane, on main and on unrelated PRs (#4458 run 36478394826: 36 of 39 failed jobs; also #4443, #4440, #4439).

Evidence

Last pass on main: 53013bf (run 36174209121, 18:33Z Sep 25). First failure: 54b48ef, [world-vercel] Attest the executor's spec version on run_started #4366 (run 36176810407, 18:58Z). The commits between were cancelled. vercel/workflow-server#1044 ("Raise a run's spec version to its executor's on run_started") merged, and so deployed, at 18:51Z that day.
Failing run from job 109117891555: the victim wrun_41M3MV6Z340GPC23968JV06E1B shows hook_created → hook_disposed → run_completed, so it was taken over. The claimer wrun_41M3MV70EY0GYXTCJDY4G7CCH9 holds hook_created and sits running, waiting for a payload the test never sends.

Root cause

The test stamps its victim with specVersion: SPEC_VERSION_SUPPORTS_HOOK_FORCE_CLAIM - 1, but the victim executes on the current runtime. The old comment said "the World decides from the persisted version alone". That stopped being true with #4366: world-vercel now attests executorSpecVersion (8) on run_started (packages/world-vercel/src/events.ts:778), and workflow-server#1044 raises the run to it. 8 is capability-only, so the raise can happen mid-run. By the time the claimer forces the token the victim really is a spec-8 reader, and the server correctly takes the token over instead of refusing. The SDK and backend behave as designed. Only the test's premise is stale.

Fix

After the victim's hook exists, the test reads its persisted specVersion:

If the World raised it (world-vercel), the test asserts the takeover: the claimer's hook has claimedFrom set to the victim, the victim ends force_claimed, and the resume reaches the claimer.
Otherwise (world-local and world-postgres keep the stamp), the test asserts the refusal as before.

This lane can't produce a victim whose runtime predates the disposal, because such a runtime never attests. The backend's integration tests cover the refusal for that case.

Testing

Local dev E2E (nextjs-turbopack, world-local): -t experimental_force → 8 passed, including this test on the refusal branch.
Biome clean; no new type errors in the changed range. node scripts/check-changesets.mjs passes (empty changeset, test-only).
The raised branch runs in this PR's Vercel lanes.

🤖 Generated with Claude Code

…executor's spec version The force-claim refusal test stamps its victim one spec version below SPEC_VERSION_SUPPORTS_HOOK_FORCE_CLAIM, but the victim runs on this runtime. Since #4366 world-vercel attests that runtime's version on run_started, and workflow-server (vercel/workflow-server#1044) raises the run to it, so the victim is a spec-8 reader by the time the claimer forces the token. The server correctly takes it over, the claimer waits for a payload the test never sends, and every Vercel lane times out. Read the victim's persisted version after its hook exists. If the World raised it, assert the takeover instead; otherwise assert the refusal as before (world-local and world-postgres keep the stamp). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

vercel · 2026-09-28T20:58:22Z

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

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

Copilot

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

changeset-bot · 2026-09-28T20:58:27Z

🦋 Changeset detected

Latest commit: 6984c5b

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

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

github-actions · 2026-09-28T21:04:13Z

📊 Workflow Benchmarks

commit 6984c5b · Mon, 28 Sep 2026 21:29:26 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	2257	2456 🔴	2462 🔴	2583 🔴	30
TTFS	stream	2102	2409 🔴	2444 🔴	2471 🔴	30
TTFS	hook + stream	2639	2790 🔴	2840 🔴	2981 🔴	30
Fan-out TTFS	Promise.all(100 steps)	763	2835	2965	3454	10
Fan-out TTLS	Promise.all(100 steps)	3448	5988	6247	9440	10
STSO	1020 steps (inline)	118	152	166	256	1019
WO	1020 steps	152985	152985	152985	152985	1
CRTT	first chunk (pooled)	84	134	148	314	28

Streams

Scenario	CRTT 1st	p75	p90	p99	CDV max	iters
paced control (100/s, 60B)	117	161	226	401	131	10
size sweep (100/s, 160B-12KB)	120	163	196	459	157	10
replay gateway-gpt-5.4-nano-2000t (1x)	134	147	171	259	201	3
replay eve-gpt-5.6-sol-2000t (1x)	182	156	197	659	609	2
replay eve-gpt-5.6-sol-2000t (2x)	106	199	276	500	219	3

📈 STSO distribution (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: 152531ms over 1019 samples

_{No main baseline with raw samples yet — showing this run's distribution on its own; the diff appears once a run on main has recorded them.}

  100-150 ms  ████████████████████████  steps 733
  150-200 ms  ████████                  steps 256
  200-250 ms  █                         steps  19
  250-300 ms  █                         steps   6
  300-350 ms  █                         steps   1
  350-400 ms  █                         steps   2
 950-1000 ms  █                         steps   1
1400-1450 ms  █                         steps   1

📈 CRTT drill-down (RTT distributions & profiles)

_{No main baseline yet — percentages appear once a run on main has recorded CRTT.}

variant  RTT 1ms→5s+      avg  p50  p90  p99     n
control  ······▂█▁····  138.2  128  226  401  3000
sweep    ······▂█▁····  139.2  131  196  459  3000
gw 1x    ······▂█▁····  128.9  127  171  259  5295
eve 1x   ·····▁▃█▁▁···    139  122  197  659  5186
eve 2x   ·····▁▂█▃▁▁▁·    168  148  276  500  7779

RTT over stream progress (avg per tenth of stream, bars scaled min→max):

control  █▄▅▅▃▃▃▂▃▁  124–160ms
sweep    █▄▃▅▁▂▄▄▆▅  128–154ms
gw 1x    ▆▅▄▅▅▂▂▅█▁  124–135ms
eve 1x   ▁▂▂▁▁▄█▂▁▃  124–192ms
eve 2x   █▂▁▁▂▂▃▄▄▂  140–247ms

RTT by chunk size (avg per log size bin, ~160B → ~12KB serialized, bars scaled min→max):

sweep  ▇▇█▄▂▁▆  138–140ms

Delivery jitter over stream progress (avg positive CDV per tenth of stream, bars scaled min→max):

control  ▂▁▆█▃▇█▆▃▂  34–48ms
sweep    ▁▆█▇▃▇█▆▄▁  48–65ms
gw 1x    ▆█▆▁▄▅▅▄▄▃  35–43ms
eve 1x   ▄▆▂▃▅▆█▄▁▅  22–30ms
eve 2x   ▇▄▂▃▇▄▃▁▃█  22–33ms

ℹ️ Metric definitions & methodology

_{Streams: first-chunk RTT (the stream-open path, before any buffering/backpressure), CRTT percentiles, and worst delivery stall (CDV max). Cells are medians across iterations; per-run values in the artifacts. No 🔴/🟢 marks until targets attach.}

_{The collapsed STSO distribution section above buckets every step gap, split inline (same warm process — pure framework overhead) vs queue-hop (fresh process — dispatch, reinit, replay). █ = main, ┃ = this run, ░ = fill.}

_{The collapsed CRTT drill-down: per-variant RTT histograms (fixed log bins, · = empty) and mean RTT/positive-CDV profile lines over stream progress and chunk size. Histograms, avgs, and profiles merge exactly across runs; p50–p99 are percentile-of-percentiles. Per-index rows live in the artifacts.}

_{Metrics — TTFS: time to first step body (in-deployment start() → first step body) · Fan-out TTFS: fan-out time to first step (in-deployment start() → first of the parallel step bodies to complete) · Fan-out TTLS: fan-out time to last step (in-deployment start() → last of the parallel step bodies to complete, i.e. when the Promise.all resolves) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · CRTT: chunk round-trip time (per-chunk write → read latency, one clock domain: deployment → stream backend → same deployment) · CDV: chunk delay variation / delivery jitter (inter-arrival gap minus inter-write gap per seq-adjacent pair; skew-free; the row is each run's MAX positive value, so one stall moves it)}

_{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 · Promise.all(100 steps): 100 trivial no-op steps started together in a single Promise.all; Fan-out TTFS is the first of them to complete and Fan-out TTLS the last, both from the in-deployment clientStart, so their gap is the spread the runtime adds across the fan-out · paced control (100/s, 60B): the control: 300 tiny (~60B) deltas metronome-paced at 100/s — zero workload structure, so it reads the transport floor and flush cadence, and disambiguates transport-wide vs workload-specific when a replay row moves · size sweep (100/s, 160B-12KB): same pacing as the control with deltas padded in rotation across seven log-spaced sizes (~160B–12KB) — rotation decouples size from stream position, so it isolates whether chunk size causes latency · replay gateway-gpt-5.4-nano-2000t (1x): raw provider SSE cadence captured at the AI gateway boundary (gpt-5.4-nano, the most popular gateway model; per-token deltas p50 208B = the modal production chunk size), replayed exactly as measured — the typical customer's workload; its CDV is the typical customer's real delivery jitter · replay eve-gpt-5.6-sol-2000t (1x): a captured eve turn (gpt-5.6-sol, the most-used demanding eve model; ~2000 output tokens = production p50 turn length) replayed exactly as measured — eve's envelope protocol re-ships the cumulative message so sizes ramp 142B→13KB; the demanding outlier tenant's reality · replay eve-gpt-5.6-sol-2000t (2x): the same eve capture at 2x — the headroom/stress row; real fast-tier models emit the same chunk sizes at proportionally higher rate, so time compression is a faithful speed model · first chunk (pooled): every run's seq-0 RTT pooled across all stream scenarios — the first chunk precedes any workload differentiation, so pooling samples one shared stream-open path with exact percentiles}

_{Replay cadences (semantic sha256) — eve-gpt-5.6-sol-2000t eaf22f5946e7c61f3c65c7006d550df180cfabd4e706254a09f22aec0cfb420d · gateway-gpt-5.4-nano-2000t 6f24ac518b6b83ff1d0e85a5fe78230db192716d66a7fc6b2fe022752001d041}

_{🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600}

_{All timestamps are deployment-side; runs are triggered in-deployment, so the CI runner and api.vercel.com sit outside every measured window. TTFS = start() → first step body (includes dispatch + any cold start); Fan-out TTFS/TTLS = first/last step completion of one Promise.all from the same anchor (the gap is the runtime’s fan-out spread); STSO/WO between step bodies; CRTT inside the workflow (excludes the api.vercel.com read path).}

_{Cold starts stay in the numbers (real bursty-workload latency, inflates P75+); Best is the warm floor.}

github-actions · 2026-09-28T21:04:14Z

🧪 E2E Test Results

✅ All tests passed

⚠️ Flaky E2E Tests (passed on retry)

These tests failed at least once and passed on a retry. A recurring entry here is a real race worth investigating.

a run can take over its own earlier hook (sveltekit · local-dev / local / node / stable)
abortParallelWorkflow: abort cancels all parallel steps (python · vercel-prod / vercel / node / production)
health check (CLI) - workflow health command reports healthy endpoints (nextjs-webpack · local-dev / local / node / stable)

🛠 Infra Events (absorbed by the harness)

Platform anomalies the e2e harness detected and worked around (e.g. a run the queue never picked up, replaced by a fresh run). Clustered timestamps indicate a backend blip; a steady drip indicates a platform issue worth escalating.

cold-start-warmup · suite warmup (tanstack-start) · at 21:11:24Z · abandoned wrun_01M3MXPTNCDCYJ8Q3Y40MYTTXW
run-pickup-stall · abortParallelWorkflow: abort cancels all parallel steps (nuxt) · at 21:14:23Z · abandoned wrun_01M3MXWCFA7YKR8GW8Y6K06H1G
run-pickup-stall · AllInOneService.processNumber - static workflow method using sibling static step methods (nextjs-webpack) · at 21:15:29Z · abandoned wrun_01M3MXYCYVNJMR3WGA1T46Y0C8

E2E Test Summary

Summary

	Passed	Skipped	Total
✅ ▲ Vercel Production	3878	739	4617
✅ 💻 Local Development	3898	548	4446
✅ 📦 Local Production	4238	550	4788
✅ 🐘 Local Postgres	4238	550	4788
✅ 🪟 Windows	340	2	342
✅ 🌐 Cross-language Conformance	68	84	152
✅ vercel-http-transport	873	153	1026
✅ vercel-multi-region	27	0	27
✅ vercel-ws-transport	591	93	684
Total	18151	2719	20870

Details by Category

✅ ▲ Vercel Production

App	Passed	Skipped
✅ astro-node	141	30
✅ astro-quickjs	141	30
✅ example-node	141	30
✅ example-quickjs	141	30
✅ express-node	141	30
✅ express-quickjs	141	30
✅ fastify-node	141	30
✅ fastify-quickjs	141	30
✅ hono-node	141	30
✅ hono-quickjs	141	30
✅ nest-node	141	30
✅ nest-quickjs	141	30
✅ nextjs-turbopack-node	168	3
✅ nextjs-turbopack-quickjs	168	3
✅ nextjs-webpack-node	168	3
✅ nextjs-webpack-quickjs	168	3
✅ nitro-node	141	30
✅ nitro-quickjs	141	30
✅ nuxt-node	141	30
✅ nuxt-quickjs	141	30
✅ python-node	66	105
✅ sveltekit-node	160	11
✅ sveltekit-quickjs	160	11
✅ tanstack-start-node	141	30
✅ tanstack-start-quickjs	141	30
✅ vite-node	141	30
✅ vite-quickjs	141	30

✅ 💻 Local Development

App	Passed	Skipped
✅ astro-stable-node	142	29
✅ astro-stable-quickjs	142	29
✅ express-stable-node	142	29
✅ express-stable-quickjs	142	29
✅ fastify-stable-node	142	29
✅ fastify-stable-quickjs	142	29
✅ hono-stable-node	142	29
✅ hono-stable-quickjs	142	29
✅ nest-stable-node	142	29
✅ nest-stable-quickjs	142	29
✅ nextjs-turbopack-canary-node	170	1
✅ nextjs-turbopack-canary-quickjs	170	1
✅ nextjs-turbopack-stable-node	170	1
✅ nextjs-turbopack-stable-quickjs	170	1
✅ nextjs-webpack-stable-node	170	1
✅ nextjs-webpack-stable-quickjs	170	1
✅ nitro-stable-node	142	29
✅ nitro-stable-quickjs	142	29
✅ nuxt-stable-node	142	29
✅ nuxt-stable-quickjs	142	29
✅ sveltekit-stable-node	161	10
✅ sveltekit-stable-quickjs	161	10
✅ tanstack-start-node	142	29
✅ tanstack-start-quickjs	142	29
✅ vite-stable-node	142	29
✅ vite-stable-quickjs	142	29

✅ 📦 Local Production

App	Passed	Skipped
✅ astro-stable-node	142	29
✅ astro-stable-quickjs	142	29
✅ express-stable-node	142	29
✅ express-stable-quickjs	142	29
✅ fastify-stable-node	142	29
✅ fastify-stable-quickjs	142	29
✅ hono-stable-node	142	29
✅ hono-stable-quickjs	142	29
✅ nest-stable-node	142	29
✅ nest-stable-quickjs	142	29
✅ nextjs-turbopack-canary-node	170	1
✅ nextjs-turbopack-canary-quickjs	170	1
✅ nextjs-turbopack-stable-node	170	1
✅ nextjs-turbopack-stable-quickjs	170	1
✅ nextjs-webpack-canary-node	170	1
✅ nextjs-webpack-canary-quickjs	170	1
✅ nextjs-webpack-stable-node	170	1
✅ nextjs-webpack-stable-quickjs	170	1
✅ nitro-stable-node	142	29
✅ nitro-stable-quickjs	142	29
✅ nuxt-stable-node	142	29
✅ nuxt-stable-quickjs	142	29
✅ sveltekit-stable-node	161	10
✅ sveltekit-stable-quickjs	161	10
✅ tanstack-start-node	142	29
✅ tanstack-start-quickjs	142	29
✅ vite-stable-node	142	29
✅ vite-stable-quickjs	142	29

✅ 🐘 Local Postgres

App	Passed	Skipped
✅ astro-stable-node	142	29
✅ astro-stable-quickjs	142	29
✅ express-stable-node	142	29
✅ express-stable-quickjs	142	29
✅ fastify-stable-node	142	29
✅ fastify-stable-quickjs	142	29
✅ hono-stable-node	142	29
✅ hono-stable-quickjs	142	29
✅ nest-stable-node	142	29
✅ nest-stable-quickjs	142	29
✅ nextjs-turbopack-canary-node	170	1
✅ nextjs-turbopack-canary-quickjs	170	1
✅ nextjs-turbopack-stable-node	170	1
✅ nextjs-turbopack-stable-quickjs	170	1
✅ nextjs-webpack-canary-node	170	1
✅ nextjs-webpack-canary-quickjs	170	1
✅ nextjs-webpack-stable-node	170	1
✅ nextjs-webpack-stable-quickjs	170	1
✅ nitro-stable-node	142	29
✅ nitro-stable-quickjs	142	29
✅ nuxt-stable-node	142	29
✅ nuxt-stable-quickjs	142	29
✅ sveltekit-stable-node	161	10
✅ sveltekit-stable-quickjs	161	10
✅ tanstack-start-node	142	29
✅ tanstack-start-quickjs	142	29
✅ vite-stable-node	142	29
✅ vite-stable-quickjs	142	29

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack-node	170	0	1
✅ nextjs-turbopack-quickjs	170	0	1

✅ 🌐 Cross-language Conformance

App	Passed	Failed	Skipped
✅ python	68	0	84

✅ vercel-http-transport

App	Passed	Skipped
✅ example	141	30
✅ express	141	30
✅ hono	141	30
✅ nextjs-turbopack	168	3
✅ nitro	141	30
✅ vite	141	30

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

✅ vercel-ws-transport

App	Passed	Skipped
✅ example	141	30
✅ express	141	30
✅ nextjs-turbopack	168	3
✅ vite	141	30

📋 View full workflow run

github-actions · 2026-09-28T21:05:15Z

Sim World

Simulated world deterministic testing for races. Traces

🟠 world-sim scenario book — 1 fail of 42 total

fence=per-spec

scenario	outcome	events	virt	replay
✅ `smoke-no-steps`	completed	3	0ms	ok
✅ `smoke-one-step`	completed	6	0ms	ok
✅ `hook-at-step-started`	completed	12	0ms	ok
✅ `hook-at-step-completed`	completed	12	0ms	ok
✅ `hook-at-hook-created`	completed	12	0ms	ok
✅ `deadline-hook-wins`	completed	7	1.0h	ok
✅ `deadline-expires`	completed	7	1.0h	ok
✅ `step-vs-timer-early-settlement`	completed	8	1.0h	ok
✅ `long-sleep`	completed	11	30.0d	ok
✅ `hook-never-arrives`	stalled	3	0ms	skipped
✅ `step-retries-twice`	completed	10	2.0s	ok
✅ `parallel-steps`	completed	9	0ms	ok
✅ `hook-on-execution-state`	completed	12	0ms	ok
✅ `peek-hook-before-branch`	completed	12	0ms	ok
✅ `peek-hook-after-branch`	completed	12	0ms	ok
✅ `peek-hook-at-registration`	completed	12	0ms	ok
✅ `race-hook-before-probe`	completed	12	0ms	ok
✅ `race-hook-after-probe`	completed	12	0ms	ok
✅ `race-duplicate-delivery`	completed	13	0ms	ok
✅ `attr-hook-before-step`	completed	11	0ms	ok
✅ `attr-hook-after-step`	completed	11	0ms	ok
✅ `attr-from-step-body`	completed	13	0ms	ok
✅ `fork-hook-after-timeout`	completed	14	1.0m	ok
✅ `fork-hook-before-timeout`	completed	14	1.0m	ok
✅ `count-hook-after-timeout`	completed	17	1.0m	ok
✅ `count-hook-before-timeout`	completed	20	1.0m	ok
✅ `stale-read-step-count-fork`	completed	20	1.0m	ok
✅ `stale-read-equal-step-counts`	completed	14	1.0m	ok
✅ `step-vs-step-fork`	completed	12	0ms	ok
✅ `step-vs-step-fork-fenced`	completed	12	0ms	ok
✅ `fence-catches-benign-direction`	completed	12	5ms	ok
✅ `in-flight-before-decision`	completed	17	1.0m	ok
❌ `in-flight-before-decision-counted`	completed	17	1.0m	ok
✅ `in-flight-after-decision`	completed	19	2.0m	ok
✅ `stale-read-step-count-fork-fenced`	completed	20	1.0m	ok
✅ `fork-hook-wins`	completed	13	1.0m	ok
✅ `fork-timeout-wins`	completed	13	1.0m	ok
✅ `unclaimed-payload-under-fork`	completed	17	1.0m	ok
✅ `claimed-payload-under-fork`	completed	17	1.0m	ok
✅ `writers-independent-step-bodies`	completed	12	0ms	ok
✅ `writers-scripted-tempo`	completed	12	0ms	ok
✅ `cancel-mid-step`	cancelled	7	0ms	skipped

Full trace: world-sim.txt

github-actions · 2026-09-28T21:10:30Z

Framework	Flow route	Step reg.	Framework output
hono	265.3 KiB (±0)	96.2 KiB (±0)	1.93 MiB (±0)
nextjs-turbopack	272.8 KiB (±0)	426 B (±0)	925.0 KiB (±0)

About these numbers

Sizes are gzip; parentheses show the change against main.
Flow route and Step reg. gate this job, on raw bytes rather than the gzip shown, at max(2%, 50.0 KiB). Framework output is informational.

6984c5b · run

github-actions · 2026-09-28T22:12:39Z

No backport to stable for 1aad998 (AI decision).

This is a test-only fix for the createHook({ experimental_force: true }) force-claim e2e test, but that feature and its tests do not exist on stable — packages/core/e2e/e2e.test.ts there contains no ForceClaim/experimental_force references at all. The change also depends on main-only behavior (world-vercel's executorSpecVersion attestation from #4366 plus workflow-server#1044), so there is nothing on the maintenance line for it to keep working.

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

1aad99884c1b3f2c394340b06d64fa27300ab7df

Copilot AI lite review requested due to automatic review settings September 28, 2026 20:58

pranaygp requested a review from a team as a code owner September 28, 2026 20:58

Copilot AI reviewed Sep 28, 2026

alangenfeld approved these changes Sep 28, 2026

View reviewed changes

vercel Bot deployed to Preview – workflow-docs September 28, 2026 21:00 View deployment

pranaygp enabled auto-merge (squash) September 28, 2026 21:05

pranaygp disabled auto-merge September 28, 2026 22:11

pranaygp merged commit 1aad998 into main Sep 28, 2026
181 of 185 checks passed

pranaygp deleted the pgp/fix-force-claim-predates-disposal-e2e branch September 28, 2026 22:11

Navigation Menu

test(e2e): expect a takeover when the World raises a force-claim victim to its executor's spec version - #4462

test(e2e): expect a takeover when the World raises a force-claim victim to its executor's spec version#4462
pranaygp merged 1 commit into
mainfrom
pgp/fix-force-claim-predates-disposal-e2e

pranaygp commented Sep 28, 2026

Uh oh!

vercel Bot commented Sep 28, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

changeset-bot Bot commented Sep 28, 2026

Uh oh!

github-actions Bot commented Sep 28, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Sep 28, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Sep 28, 2026

Uh oh!

github-actions Bot commented Sep 28, 2026

Uh oh!

Uh oh!

github-actions Bot commented Sep 28, 2026

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

pranaygp commented Sep 28, 2026

Problem

Evidence

Root cause

Fix

Testing

Uh oh!

vercel Bot commented Sep 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

changeset-bot Bot commented Sep 28, 2026

🦋 Changeset detected

Uh oh!

github-actions Bot commented Sep 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📊 Workflow Benchmarks

Uh oh!

github-actions Bot commented Sep 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🧪 E2E Test Results

⚠️ Flaky E2E Tests (passed on retry)

🛠 Infra Events (absorbed by the harness)

E2E Test Summary

Uh oh!

github-actions Bot commented Sep 28, 2026

Sim World

Uh oh!

github-actions Bot commented Sep 28, 2026

Uh oh!

Uh oh!

github-actions Bot commented Sep 28, 2026

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

vercel Bot commented Sep 28, 2026 •

edited

Loading

github-actions Bot commented Sep 28, 2026 •

edited

Loading

github-actions Bot commented Sep 28, 2026 •

edited

Loading