Tux Racer bounded transport: runtime executed, evidence retrieval blocked

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 canonical remote compile and one original guest run occurred. The guest ended at its unchanged 90 CPU-second limit (SIGXCPU24). No PNG was retrieved or inspected, and detailed poll/dispatch logs remain on the stopped Boat. Practice, race, main/worker poll deltas, scheduler gates and cause remain unqualified.

All three retained archives (14383183 bytes) transferred in place, using 11264-byte raw chunks and API arguments below 16384 bytes. Incremental offsets/digests, periodic full hashes and final remote hashes matched. The remote verified all 454 staged files, then removed the historical module before compilation. No new local archive, full checkout, snapshot pull, old-Boat resume or synthetic replay occurred.

The first local supervisor hit its own 90 CPU-second limit (shell exit152). Its compressed log prefix was preserved, with the incomplete final member sealed by appending a final deflate block/trailer. A changed supervisor reduced repeated accounting scans to periodic complete measurements, retaining per-transfer checks and original per-process limits. It continued on the same Boat only after the remote prefix matched the source. Completed archive bytes were not resent; no guest allowance was reset. See local-supervisor-terminal.json and the as-run lifecycle.py/continue-staging.py. Missing-origin and missing-current-main-object diagnostics were preserved; owned configuration and exact-main fetch resolved them.

The single transport stream stayed below its 256KiB forecast. The later Git publication journal is separate so publication cannot mutate the sealed transport evidence. transport-validation.json records decoded identity and record count. No per-chunk receipt files or duplicated archive were created.

Local PythonDATA128MiB, Git-childDATA256MiB only, supervisor128MiB/group512MiB, remote group2GiB, Node heap512MiB, CPU90/wall120, generated-file12MiB and separate capture512KiB controls were retained. Compiler files have the original4MiB limit; the canonical compiler holds 20731058 WAT bytes in memory without combined.wat. CWD rejections, a legitimate655360-byte file and separate output-overflow control passed. Final Python syntax and actual-manifest selection arithmetic passed.

Historical runtime source is a998bf36b108275335af501d8ae774731495b9b2, separate from the report's current-main parent in report-parent.json. Source-manifest SHA256 b4c8e15abac596f027685b227548c435263355ac5ef6444c2d6bc3a7649198bb binds141 pins and 128 recursive includes. Existing closure/observer acceptance was reused after archive, observer, manifest and unchanged 157-file filename-parser checks. Runner SHA256 f96e9bb924700ee571e2904e097f80742ff55638399898ae1dc32454af05b02d; observer SHA256 01f4de4099a0e60c56cf6ea109f82ae12e1c42b6ba15309d0411b10fe8029040. Expected module1881806 bytes, SHA256 5a39225e1a8381ce1c4530d2ce7cd6311bd75576d10968c20e963baf033d41eb. The transferred remote worker's strict size/hash assertion passed before runtime: the recorded failure is from the subsequent guest invocation. Module-manifest and startup/compile receipt contents were not retrieved; no direct local module rehash or current-main runtime qualification is claimed.

The collector incorrectly required all four PNGs (652097 bytes) to fit before selecting. Three have identical SHA256; actual-manifest selection of title136760 plus one distinct171779-byte frame would total308539, inside512KiB. Equal hashes do not establish visual content. No selected image was copied or inspected; no final after.png was produced. runtime.stdout58468 bytes has SHA256 bdecccd0e99d58aefa5758d784c8b0f519abd7d96a53c4bcb089c812b185dbd7. Its observations and saturation remain unknown locally. capture-manifest.json preserves remote file identities. The collection failure triggered delegated cleanup before any logs/images were copied. Supported stopped-file CLI download exposes snapshot pull; that prohibited full-layer route was not retried.

Next prerequisite: coordinator-authorized bounded exact-file recovery of the existing snapshot's title.png, one distinct menu-candidate image, module/startup/ compile/runtime JSON and runtime.stdout, followed by inspection. No unchanged runtime replay is justified. Only compact task report paths are published on current main; production source, GLTron, predecessor evidence and shared indexes remain unchanged. No workers, Telegram or public deployment. The coordinator appends messageboard-note.txt because the board exceeds the task file-size limit.