ReVolt published atomic operator driving attempt — 2026-11-18

Manual acceleration, steering, course consequence and ordinary Quit remain unverified. The single new scope closed permanently UNKNOWN at 13:22:53.311 UTC when live action admission observed an ordinary game-data loading dialog for nhood1i.bmp. No second input DOWN was sent, and no runtime request followed closure. The scope was not reopened or retried.

Evidence is scratch/runs/20261118-revolt-published-atomic-command-driving/. The preceding loading-readiness note, sealed result and recovery were read without touching either old closed scope. All 463 existing media pins and retained module a6002d5dbcfeb534a0eadd223da616e525aa1542dad2bde381fe54e00ee862f8 verified offline. The new browser used coherent published Git 72cd365561b20e2f182bb37fa46146106f88b179, actual published startup readiness and UTC handling, with that retained module whose compiler-source recovery is f6962ba5b1cf2829a66f5cc4d80b293c30719b37. Child executing module/roles remain UNKNOWN. No unchanged compilation, qualification campaign or common-helper change was performed.

Admission waited while actual free space was below 1.5 GB. The concurrent capacity worker recovered space; this worker did not clean foreign files. Launch occurred only after an actual observation above the existing floor. The runtime watchdog's sampled minimum was 1,561,182,208 bytes; this is not continuous lifetime proof. Prelaunch observations below the floor remain recorded separately.

Published tools/revolt-operator-command.cjs carried six complete atomic command records. Fresh whole front-menu images were personally viewed. One finite 100 ms ArrowDown reached the page as a trusted event, with independent prearmed release, physical UP0 and actual release wait/EOF. The next whole images still showed Start Race highlighted; this establishes no selection or driving consequence. A subsequently chosen 500 ms Down was refused during the first live-owner check because loading now obscured the output, before release arm or DOWN. The exact reason the short first gesture had no visible effect is UNKNOWN. Loading alone does not prove manual race entry or a demo, and neither is claimed.

The attempted next capture after closure was refused locally by the published operator before command publication; there was no endpoint request. Strict visibility, freshness and permanent-closure rules were preserved. An expected loading obstruction is not evidence of a runtime defect warranting weakened admission or an unchanged retry. No binding verification, throttle, steering, race HUD, speed/course/checkpoint effect, ordinary Quit or native guest exit was observed.

Chrome exited 0 during host cleanup, as did the individual Xvfb/openbox children; these are not guest Quit. The enclosing launcher and supervisor returned 1 with both EOF receipts, the independent finite watchdog joined, and the native supervisor reported no leaks. Selected named whole images, actual waits, PID absence, native-exit limitations, Git binary diff, unique-wrapper patches and recovery recipes are retained. No source snapshots, media copies, encoded image payload copies, workers, boxes, Python, Wine or deployment were used. Box ID null, state NOT_CREATED, expiry null, stop receipt null. Ownership is released and this single-task worker stops after sealing result.json last.