Tux Racer retained runtime: title and main menu confirmed

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.

Personally inspected exact 640×480 title.png and before.png on 2026-10-30. The first shows the Tux Racer splash and “PRESS ANY KEY TO START”; the second shows the main menu: Enter an event, Practice, Credits and Quit. Practice, course selection, race/gameplay and ordinary Quit are not demonstrated. The retained practice.png and course.png have the same length and SHA256 as before.png: their names describe attempted capture points, not successful transitions.

Actual retained observation

Exact log observations (line numbers in runtime.stdout):

Collector correction and acceptance

The predecessor collector added all four PNG sizes (652097) before selecting, incorrectly rejecting the set. The corrected reusable collector in test/tuxracer-exact-log-runtime-disposition-oct30/collector.py takes explicit name/length/SHA pins, rejects ambiguous/unsafe names, selects and deduplicates by (length,SHA), then enforces the512KiB ceiling before any fetch. Verified local representatives are reused; new files use exclusive creation and bounded 11264-byte chunks with final full length/SHA verification. It never packs or discovers unrelated remote files. The predecessor supervisor remains immutable.

Actual selected set: title136760 + before171779 =308539 unique image bytes; plus runtime.stdout58468 =367007 bytes, below524288. Four tests pass: old duplicate-image reproducer and unselected oversized file; genuinely oversized unique selection rejects before fetching; local reuse plus exact chunk recovery; pin/name conflicts and corrupt local content reject. The same collector verified all three actual files with zero fetch calls. These are collector tests, not guest acceptance. Local wrapper checks separately passed a legitimate655360-byte generated file under12MiB FSIZE and rejected600000-byte output under512KiB capture; omitted/root/donor cwd rejecting controls passed. Git DATA256MiB applies only to Git children, Python DATA128MiB only to Python children. No Node execution needed. The unchanged canonical filename parser receipt was reverified and reused; there is no new filename-bearing guest invocation.

Recovery, resources and lifecycle

Wrapper qualification gap: initial local API clients used the specified soft DATA/CPU/FSIZE limits with inherited infinite hard limits. Review corrected hard child bounds to DATA128MiB (Git256MiB), CPU60/60 and FSIZE12MiB, preserving stricter inherited limits; wrapper controls and collector tests passed on that corrected configuration. Initial receipts are retained, not retroactively qualified. The remote exact-file reader itself set DATA128MiB, CPU60/60 and FSIZE12MiB hard/soft.

New fork bx_b9s6w3bm created2026-10-30T09:24:14.923Z, finiteTTL1800, original expiry09:54:14.892Z. This task explicitly owned snapshot-stop. Independent watchdog armed before API smoke, with separate operation files/logs and20/23/25 minute cutoff/handback/shutdown schedule. Supported explicit-ID API recovered only runtime.stdout, in six chunks of at most11264 raw bytes; every request envelope was below16KiB. No new guest process was launched; API subprocess groups were reaped. The prior worker had already reaped the original guest group.

Recovery recipe: use selected-verification.json local paths first and verify exact pins. runtime.stdout is task-owned beside completion-receipt.json; title.png and before.png remain in the parent capture directory. The original stopped source and new post-recovery snapshot retain the remote exact path /home/user/tuxracer-render/capture/runtime.stdout. No further provisioning or access is authorized by this report. Compact receipts and corrected collector are published; raw media, historical denials and as-run API records remain local. Coordinator appends messageboard-note.txt; this worker does not write shared main.