MW3 repaired Worker gameplay attempt — 2026-11-07
The single authorized original-runtime attempt stopped before MW3 navigation.
The first blocker is the retained browser driver's DevTools endpoint startup
read: original/endpoint.json contains {"debugPort":0} with no browserPath.
At 14:19:59.103Z, constructing its WebSocket raised SyntaxError: TypeError: Invalid URL at browser.cjs:76. Chrome's stderr records a valid endpoint on
port 37039. An incomplete DevToolsActivePort read is the supported inference:
the driver waits for file existence, then immediately reads/splits its contents
without waiting for two complete valid lines. The original file was removed
during normal profile cleanup, so its bytes are unavailable.
No CDP connection, original guest Worker, owning presentation, reviewed pixels, native input, cockpit, movement, turning or firing qualified in this attempt. No original gameplay or emulator-defect claim follows. The fixed deadline was 14:19:58.639Z–14:44:58.639Z; the terminal failure was not replayed. No second runtime, old-box action, handler bypass, guest/config/clock edit, cooperative fallback acceptance, readiness relaxation or repeated input fixture matrix occurred. The six original driver helpers remained byte-identical.
Evidence: scratch/runs/20261107-mw3-repaired-worker-gameplay/.
The predecessor support repair was published and released before preparation.
Its strict preflight rejected concurrent changes in three render files. As its
recipe requires, a fresh local support-boot proof was performed in this owned
directory before allocation; predecessor evidence was not overwritten. That
generated-PE proof reproduced signature-404 failure before repair and actual
production guest Worker execution after repair. Recovered executing module
bytes, owner identity, HTTP bodies and normal cleanup passed. Its audit records
the three source changes explicitly; all successful responses match the fresh
pins. This proves support startup, not original gameplay.
The 300-file runtime closure and its manifest were uploaded individually and
all 300 inputs verified remotely before launch. The generated signatures,
api_table.json, vendor dependencies, genuine MSVCP50/Mech3Msg and normal
configuration were retained. All 33 original registry HTTP bodies passed
before Chrome launch. Exact staged source: main
bb6509322426db9cade7503b07ce6a08e15f28a2 plus retained relevant binary patches;
the concurrent render changes were later published by their owner as
dcbc8248a606d9594634213242063960316bdb4d. Staged WASM:
2,182,493 bytes, SHA-256
e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467.
No original executing-module identity exists. Media remain referenced by
existing path, length and SHA-256; no source/media archive was made.
One UUID-keyed POST /sandboxes created bx_vtxbjy65. Chrome exited normally
with code 0; driver/Chrome processes, server/debug ports, profile and command
writer were absent. No command was queued. Eighteen unique evidence files,
24,764 bytes total, were recovered and SHA/length verified. Seventeen were
downloaded; the final shutdown JSON was recovered byte-exactly from the retained
remote stdout and checked against its remote SHA/length. Under explicit shutdown
delegation, normal stop was requested at 14:20:46.784Z and completed at
14:20:48.553Z, forced:false. Confirmed final state: archived,
archiveAfter:null; original expiry was 15:19:23.633Z.
Local disk checks before allocation and retrieval exceeded 2,000,000,000 bytes. The one-second monitor during provisioning/runtime/recovery sampled a minimum of 2,853,285,888 bytes; the support browser monitor also stayed above the floor. This is sampled evidence, not a continuous guarantee. Focused support boot and closure audit, remote pins/HTTP verification, retrieval verification and cleanup checks passed. No production code changed or new build was needed for this documentation-only result.
Next: repair and regression-test complete DevTools endpoint readiness before a separately authorized fresh original attempt. Preserve the strict original Worker/presentation identity, immutable reviewed pixels, exact numbered ACK, independent UP and sticky UNKNOWN gates. This bounded assignment stops here.