Re-Volt manual checkpoint attempt, 2026-11-15

The sole software original stopped on its first causal failure: the second full-scene capture exceeded the fixed three-second operation bound. Permanent UNKNOWN was written at 16:50:08.322Z. No original input was sent. No checkpoint, lap, race result or native Quit was reached, and WebGL was withheld.

Run: scratch/runs/20261115-revolt-current-manual-checkpoint-progress/. The assigned runtime order is Sims1497762, GTA21571459, then this worker. Both predecessors must explicitly release source, build and runtime. This worker must personally verify their current direct native/watchdog/supervisor-child waits with both EOFs, absent recorded PIDs/process groups and free locks before using shared source, helpers, modules, builds, native fixtures or browsers. Historical UNKNOWN records remain UNKNOWN; missing ancillary historical receipts are not new admission conditions.

The Sims predecessor released at 16:05:52Z. Personal verification checked its release SHA-256 aff6c8407701d44b67448ae51d9a3d310c4e14705ef118b0a236caddf0e22f4b, 11 linked evidence hashes, 168 actual-wait/both-EOF records and current absence of 309 recorded PIDs and process groups. sims-handoff-personal.json records these checks. Q3's preceding release was also verified against 76 actual waits and 372 absent PIDs/groups in q3-handoff-personal.json. GTA2 released at 16:28:32Z, SHA-256 da2c72760341c6b843a02ab527a4bfdf2e83c1c1a9daaf80f7e1798dbea77674. Personal checks covered its named evidence hashes, 101 actual-wait/both-EOF records and 110 absent PIDs/groups. Both locks were acquired and released; all 419 recorded Sims/GTA2 processes/groups were absent before heavy start.

The November 12 paired-driving note records a caller failure: combined keys use action:"key", keys:[...], while unsupported action:"keys" failed before dispatch. This task requires fresh qualification of every command form against the current native fixture, including independent physical release, source, backend, scene freshness and permanent UNKNOWN guards. Old scratch controllers and private position, heading and route probes are not authority for this run.

After qualification and the required locked build and publication, the allowance is one ordinary software browser original with real ticks and defaults: native 1200 seconds, independent watchdog 1220 seconds and an irreversible 180-second Quit reserve. Only visible native checkpoint/lap/race progress, owning-backend proof and complete direct closure permit one separate WebGL arm at the same bounds. The first causal failure ends pairing.

Driving must use full-scene personal review, no older than five seconds in game or thirty seconds in menus, with a new nonce and intent for each 80–1400 ms gesture. Independent UP must occur within 1750 ms; operations have a fixed three-second bound. No capture or thinking while held. A written UNKNOWN closes the controller permanently with zero later requests, input, replay or rebind. Only positive native UNSENT permits a genuinely new capture/review/intent.

tools/revolt-manual-controller.cjs accepts singular action:"key", checks the actual owning renderer and live app/worker/module/canvas identity, requires all physical keys UP before DOWN, and prearms a separate release process. Every operation has a three-second deadline. Expired scenes permanently close because this browser path cannot supply a positive native UNSENT receipt. Written UNKNOWN closes the CDP transport; subsequent cleanup uses OS signals. The trace records request method/time/count so zero later requests can be checked without reconnecting. Fixture-only counter reads are unavailable when the original is selected.

test/test-revolt-manual-checkpoint.cjs qualifies policy, actual release children, EOF fallback, wrong-owner refusal and permanent transport closure. Its generated x86 PE creates a real D3D3 device, draws a triangle through the owning software backend, and observes ordinary GetAsyncKeyState transitions. The final fixture delivered all eleven non-Escape keys and both supported Up/steering combinations, including 80 and 1400 ms bounds. Native counters confirmed every DOWN and release; Escape called native ExitProcess(0). Independent fixture checks refused a different source digest and backend. Native USER scene-context tests passed modal transition and focus-change refusal. These are authored fixture results, not original gameplay evidence.

The full locked build passed. Protocol controls passed; stale-scene and three-second timeout controls retain permanent UNKNOWN and zero later requests. The run preserves actual native/watchdog/supervisor-child waits and both EOFs. Qualification also found a partial DevToolsActivePort startup file. The controller now waits for both valid endpoint lines within three seconds before creating a connection; the focused test covers partial and complete files. One timeout fixture first returned Chrome's "Promise was collected" error; retaining its fixture-only promise produced the intended three-second timeout. Both earlier fixture closures remain recorded; no original was involved.

Evidence will record exact Git SHA and relevant binary diffs, media path/hash pins, compact logs, selected result-named personally reviewed full PNGs and direct closure. No source/media/WASM/frame/capture bundles will be retained. Box: none created; state NOT_CREATED, expiry null, stop receipt NOT_APPLICABLE.

Original outcome

Implementation commit abf5d6bb61786977b524df778787783a431e4a8b was committed on main and strictly pulled/pushed after the full locked build and focused tests. Immediately before the original, personal closure checked 131 actual wait/both-EOF records, 83 recorded PIDs/groups absent, both locks free and more than 4 GB free disk. The run pins 766 source/module/media inputs; relevant shared uncommitted changes are patches, not a source archive. The original EXE remains SHA-256 58ba4835e6607eae62be4e023ef989172cb519c78f34811acba547e9e0e3581a.

The ordinary registered re_volt_demo browser started at 16:49:43Z with real ticks, a native 1200-second deadline, independent watchdog at 1220 seconds and the final 180 seconds reserved irreversibly for Quit. The first personally reviewed full screenshot showed the Acclaim London splash. Its owner was the actual legacy D3D endpoint 1, backend software, no WebGL adapter, with 83 completed software draw calls. Guest and owning renderer module digests both matched 40cf68a2d8ac094b2dbeea501f9f247e21cf3e2a1df505baac4ba838eb671621. These observations prove startup rendering only; no speed, FPS or hardware rendering claim follows.

capture menu-second timed out before producing its PNG. The final issued request was a Runtime.evaluate in the capture's live-observation sequence. The trace contains 190 requests, zero input requests and zero requests after the UNKNOWN record. There was no replay, rebind, retry or later runtime inspection. The missing image is not reconstructed. This is a bounded capture failure; its deeper runtime cause remains unknown, with no speculative engine fix. Native Quit is unproved. OS teardown separately joined Chrome with code 0 and the controller with code 1; the native/watchdog/supervisor-child receipts have actual waits and both EOFs. Host shutdown does not establish game success.

result.json, original-permanent-close-proof.json, direct-closure.json and selected-screenshots.json index the evidence. Only two selected personally reviewed PNGs remain: the original splash and the authored native software fixture. Unselected image hashes are retained without image bundles. All historical and new UNKNOWN records remain closed. Further work must investigate capture latency in an authored fixture; this task authorizes no original retry.