Re-Volt native race attempt, 7 November 2026
The first blocker was a launcher deadline mismatch before Chromium spawn. No original Re-Volt browser or guest launched, and this attempt adds no car recovery, checkpoint, lap or sustained race progress. The October 31 repaired default-worker race, ending with an overturned car, remains the accepted native gameplay evidence. No startup diagnosis or emulator repair was repeated.
Evidence: scratch/runs/20261107-revolt-native-lap/.
Candidate: re-volt-demo; registered app: re_volt_demo.
Qualification and preserved original fixture
All 1,490 prior Forsaken qualification pins were checked and matched before
selection. Hash-identical identity, stale-scene, exact-ACK and independent key
release controls were inherited from
20261107-forsaken-driver-recovery, rather than repeated. Small selected helper
inputs were copied into this run; no source tree or media archive was made.
The selected runtime contains 1,058 pins, including the original 443 installed
Re-Volt files and browser manifest. The EXE remains SHA-256
58ba4835e6607eae62be4e023ef989172cb519c78f34811acba547e9e0e3581a.
Every selected pin matched locally and remotely before and after the attempt.
The published generic backbuffer attachment repair was reused without changes.
The final driver's local generated fixture used actual Chromium production
guest/render Workers, with recovered guest and renderer module SHA-256
e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467.
All 17 executed repository imports were pinned. A personally reviewed generated
caption/white-canvas capture preceded one native ArrowUp pulse; trusted DOWN
and UP, release armed before DOWN, and exact command ACK passed. This was a
helper test, not Re-Volt gameplay. The 1024×712 browser viewport remained
unemulated and stable, with Chrome 151.0.7922.108. Local Node was v24.18.1.
The driver, Chrome, both ports, profile, writer and held input were cleared.
The module inherits the prior qualification's source identity
1f831717cd0dec63265ff0cde43eec4d81c8da9f and recorded
lib/wininit-boot.js new-file patch. source-commit.txt records this attempt's
checkout SHA; it is not substituted for the module's compilation provenance.
Relevant tracked diffs and owned helper inputs are retained as patches. Git
supplies source recovery.
Exact first blocker
A persisted UUID authorized one 2,400-second box, bx_825gbcst, created at 12:05:22Z, originally expiring 12:45:22.695Z. Serial uploads completed all 1,058 pins without a transfer error. Remote hash verification, JavaScript syntax checks and launcher dependency imports passed. Remote Node was v24.22.1; Chrome was 151.0.7922.108. Free space stayed above 2 GB.
Before the original launch, a generated production-Worker check of that staged
driver was attempted. The launcher supplied the immutable browser deadline
12:40:22.510Z, chosen as allocation plus 35 minutes. At 12:08:27Z the
driver rejected it at browser.cjs:10:
assert(Number.isFinite(deadline) && deadline > start && deadline-start < 30*60000);
About 32 minutes remained. The successful local qualification had used a
10-minute deadline and therefore did not expose this launcher/driver contract
mismatch. Choosing 35 minutes was this worker's error; this is not an emulator
or original-game failure. staged-capture-check-remote-result.json and the
SHA-verified staged-check.log preserve the assertion. Final staged Chromium
qualification did not pass. No guard was relaxed, deadline changed, command
replayed or original launch attempted afterward.
Next: validate the complete launcher/driver deadline contract with a window strictly below 30 minutes before allocation and original launch. Reuse these unchanged fixture/runtime pins and passing helper controls, then pursue native recovery and controlled race progress on a newly authorized original runtime.
Recovery and delegated normal stop
Terminal verification confirms all 1,058 pins unchanged, no owned runtime
processes, no original directory/log, no staged browser process file, no
profile, writer or commands. No remote Chromium, ports, live modules or held
input were created. The unique remote failure log is 924 bytes, SHA-256
a6f5173a9cca89ea536e1a3b821178625e58109dc73a8dda113bf7e8bcf8d1b4,
retrieved and verified before the task's explicitly delegated normal stop.
Stop completed 12:09:13.495Z, forced:false. Final state is archived,
active expiry null. There is no running assigned box to hand back. The local
qualified live module is retained; no original live module exists to recover.
Evidence inventory and result.json are published last.
No guest code/config/save/memory/clock edits, replacement DLLs, source changes, build, FPS/audio/parity claim or fabricated gameplay progress. Publication is documentation only.