TuxRacer prompt native Practice click
Historical source last updated, 2026-10-30. Runtime and implementation claims below describe that dated source; see current app notes and source for subsequent changes.
One original guest executed using the exact retained runner/module and unchanged production wrappers. The controller replaces manual decision-file waits with a bounded image-poll condition. The native Enter pair led to the original MainMenu. The detector matched600/602 white Practice-label pixels, rejected the title in preflight, then sent click320,260 within0.1712ms of its live menu observation, 5.008s after startup. Mouse down/up were dequeued and DispatchMessageA-dispatched at batch10600. Captures at10779 and11087 were inspected: MainMenu remains visible. Practice entry, race and gameplay are NOT established; cause remains unknown. No state mutation, audio unlock, forced mode change or second guest occurred.
Guest exit0; wall7.170s, userCPU8.267s, peak process-group RSS300097536bytes. CPU60/wall90/heap512MiB/group2GiB enforcement remained. Canonical mount validation ran before the guest, enumerating157 actual files with comma-name handling and exact runner/module hashes. Node256 startup, real PNG read/invalid rejection, exact production parser and actual stdin-pipe command transport, final validator, and positive-menu/negative-title matching passed before startup. No whole build or broad passing acceptance group was repeated. GeneratedFSIZE12MiB differs from 512KiB per-stream/4MiB aggregate capture; GitDATA256MiB is child-only and Node inherits unlimited DATA/AS. Parent wrapper receipt is reused unchanged.
Full original PNGs/raw logs and observers were losslessly archived remotely, with per-member SHA readback. Selected local images are explicitly320x240 display derivatives. The only fork was bx_rht9232f, TTL1800, created12:22:03.632Z, expiry12:52:03.590Z. Source snapshot/stopped timestamps and retained archive SHA were checked before deployment. A watchdog was armed before the first APIexec; its conservative cutoff closes the box at20min if owner cleanup fails (earlier than nominal25min shutdown). Actual owner close completed snapshot12:24:56.546Z, stopped12:24:56.585Z, with postrun snapshot identity verified. No box remains live.
Evidence: test/tuxracer-timely-practice-input-runtime-oct30. The parent retains previous SIGKILL and late-fd failures. Shared root/main/Telegram/public hosting were untouched. This is a bounded controller and investigation-evidence change, not current-main qualification or a production compatibility fix. All inherited physical roots plus actual task rollout/launcher streams are charged with unchanged 8MiB work and8MiB publication reserves; RAM admission is off. Completion receipt and a separate messageboard note are handed back to the coordinator.