MCM validated foreground: fresh quarry progress

Evidence: scratch/runs/20261120-mcm-validated-foreground-quarry-progress/. One fresh original followed the ordinary video-memory OK, name MCM, Single Player Event, Stunt Quarry, Practice, T-rific, yellow bike and Start route. The full frames were manually reviewed before each admitted input; admission ages stayed within the unchanged 12-second bound. No previous runtime resumed.

The module was recovered specifically from the validated parent run 20261120-mcm-process-group-guard-build-quarry/compiled.wasm.gz: SHA-256 f5ae1ac84e3d5e13bb093aca53b8aa2fe18c000cc891587a5d75b46eb559b2ba, 2,420,767 bytes. Actual Worker bytecode matched it. HTTP sources were reconstructed in memory from the parent's 9d601802c0cccabcd8ba2da645e26637a0e55ef0 baseline and exact recorded runtime diff; the parent's source responses were hash-checked. This preserves the matching region map and imports without changing shared production files. All 311 existing media references matched, with no copies. The committed foreground repair is da970c819deb65c4d65bc5c5e2e4bf44673089f8. Its unchanged causal/scalar/window regressions, whole-process-group cleanup proof and passing guarded build were reused; no diagnostic or build repeated.

original-run/quarry-loaded.png shows the initialized quarry behind the rider. Its actual d3dim-gps owner identifies a live WebGL executor/context, recovered module and active PRESENT stream. Requested WebGL alone is not the evidence. A 1,501-ms ArrowUp hold produced forward progress, a trail, changed camera distance and an increased speed gauge in throttle-consequence.png. A 1,204-ms ArrowUp+ArrowRight hold then changed the heading and quarry wall alignment, with a curved trail in turn-consequence.png. Both holds have completed independent release receipts and passive page/renderer samples. Counters are execution observations, not proof of individual DirectInput polls or steps.

Ordinary Quit remains unproved. Escape was admitted from the reviewed turn frame at age 8,091 ms. During its hold's passive sampling, the page identity read threw current D3DIM GPS publication required. The adapter closed permanently at this first UNKNOWN. Its release timer fired after 101 ms, but the failed hold is not a completed success receipt. No subsequent capture, input or endpoint request was made. The exact failing predicate is retained; the evidence does not establish which publication condition changed or show the resulting menu. Browser termination is cleanup, not native game Quit.

The unchanged corrected guard supervised the entire owned process group with an independent finite disk/deadline watchdog. All recorded live samples stayed above 1.5 GB. Direct browser and board-child joins include stdout/stderr EOF; the native receipt reports no leaks and no supervisor termination. The tmpfs profile was removed. The failed overall run preserves the achieved driving consequences and the precise exit-path observation boundary. No workers, Python, Wine, source/held-region edits or public deployment occurred. Localhost box ID is null, state NOT_CREATED, expiry null, stop receipt null; root retains shutdown ownership and this worker cleaned up its own processes.