Motocross Madness original race attempt — 2026-11-07

The original reached the video-memory prompt only. The first blocker was the run-specific scene freshness guard refusing Enter before dispatch; the worker then incorrectly retrieved a nonexistent post-input capture. No original input had effects. Race entry, ordinary throttle and distinct steering remain untested. No emulator defect is demonstrated and no production code was changed.

Evidence: scratch/runs/20261107-mcm-original-race/.

Before allocation, the duplicate generated-closeout retrieval was removed. failfast-controls.json rejects the old duplicate and executes the actual new prerequisite gate with an injected local retrieval error. Only generated finish runs; neither verification nor original launch follows. Seven controls execute the actual production direct-initializer IIFE. Actual renderer/input executor controls cover uppercase RIDER with balanced character edges and Enter, the intended literal menu points, capture, ordinary throttle and separate steering holds and quit. Atomic ACK, UNKNOWN/no-replay and invalid-duration controls pass. The supported direct route was reused without catalog filtering or mixed-case name attempts on the original.

One fresh boat, bx_8exqvc87, was created at 07:00:48.908 UTC using a persisted, fsynced UUID Idempotency-Key. Remote Surface4/7 COM/vtable-tail controls passed against a prepared and consumed retained fixture module. Native Chrome preflight reported trusted RIDER keydown/keypress/keyup triples and balanced Enter, plus five balanced arrow/Enter pairs. Invalid names and durations emitted no events. Those checks ran on about:blank, not on the original name screen.

The generated dx_boids guest executed in a Worker. Its owning renderer target FED782F4B4132CAFA0BF1E8B0C171CE0, session EDB0E1FA8E6230DA442E0CE0C12A20BA, owned endpoint 1, legacy/WebGL. Completed fences advanced 46 → 54, control error 0, adapter present, endpoint failure null, guest fallback count 0 and completed software draws 0. The current GPU vendor/provider string is unknown: it was not captured, and earlier Intel provider observations are not evidence for this run. The generated sample boundary scene was personally inspected. The generated native COMCTL property sheet and its disappearance after ordinary balanced OK at (173,418) were also personally inspected. Both generated browsers closed normally before original.

Exactly one original browser launched at 07:03:36.364 UTC, using ?debug&threads&d3d-renderer=webgl&app=mcm. The startup capture at 07:03:53.661 UTC shows the ordinary video-memory test prompt with OK/Cancel; I personally inspected it. The attempted 100ms Enter reached the guard around 07:04:08.430 UTC, about 14.8 seconds after capture, exceeding its 12-second limit. Numbered ACK 0 reports refused-before-dispatch, effects 0, refreshRequired true. No keydown occurred. This was a recoverable refusal, but the worker incorrectly issued an unconditional retrieval of after-memory without obtaining a successful input ACK. Remote stat raised FileNotFoundError because that capture was never created. This is a worker workflow failure, not guest behavior. No refresh, input retry or further original launch followed. Only ordinary quit was sent afterward, successfully ACKed as command 1.

The run-specific caller was subsequently corrected: refused ACK now exits 3, and scene-step.py runs request and retrieval sequentially with check=True. scene-step-controls.json injects the refusal and verifies no subsequent retrieval or original launch. This correction was tested locally only; it does not turn the failed original attempt into a success. A future fresh assignment must use that checked scene step, obtain and inspect a fresh capture before input, and branch on ACK status before requesting resulting evidence.

The original guest Worker executed module SHA-256 e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467, 2,182,493 bytes, equal to the staged standard module and captured from actual Workers. Source staging pins main bc81404b9318e4e41350d2aa155aada63d92355d, relevant and all-tracked binary diffs, the untracked wininit-boot patch and owned scratch-input patches. This identifies executed bytes; no fresh-build provenance is inferred. Chrome was 151.0.7922.108, V8 15.1.206.16. At the original prompt there was no owning D3D renderer endpoint, so generated WebGL completion does not establish original gameplay rendering.

All 311 registered original inputs, 45,460,823 bytes, match the prior authentic inventory and before/after hashes. MCM.EXE remains f0370d1d526be46eaf6ea5f941f185a393a8432baec695e1529f8672a314a71b. The installation-root VFS paths, working directory and source media/config/save inputs were unchanged. No original name/profile was entered. All 938 staged pins matched remotely before original and at cleanup. All 1,491 complete successful HTTP responses match pins, with zero unmapped successes. Non-200s identify build-info, auth-user, favicon, optional icons and the optional font bundle endpoint. Availability checks do not establish race execution.

All 107 remote artifacts were retrieved or deduplicated against identical owned bytes, and verified. Chrome exits were 0. The initial cleanup census saw the original controller still exiting; the subsequent read-only terminal census verified all six browser/controller PIDs absent, all six ports refusing, and all three private profiles and writer locks absent. The static cleanup label pending: UNKNOWN; never replay is not an outstanding command: actual ACKs identify the refused Enter and successful quit.

Delegated normal stop stop_0b5bc1cdaa7cc7c1 completed 07:04:52.326 UTC, forced false, error null. The box is archived, active expiry null. Allocation through completed stop took approximately 244 seconds; work and publication stayed within the 35-minute assignment limit. Local free disk measurements stayed above 2 GB. The local board watcher was stopped. No stopped-box resume, held-risk retry, nested worker, source/media archive or public deployment occurred. No motion, frame-rate, audio or full27 claim follows.