SuperTux first-exit attempt, 2026-11-08

The first-level exit and unlock remain unverified. One fresh original stopped on its first sticky UNKNOWN, before the first ice pillar. The last personally reviewed native Pause image shows score 0, coins 0, four lives and timer 286, with Tux grounded. No death was observed. No replay, second life, second browser or second box followed.

Evidence: scratch/runs/20261108-supertux-first-exit-reviewed-2330/. review/pillar-rise.png, control-summary.json.gz, remote-inventory.json.gz and retrieval-verified.json.gz identify the reviewed result and recovery. Historical 675-point/23-coin progress and the 2301 first-enemy stomp remain separate guidance; neither was reproduced by this attempt.

Preparation and actual attempt

Q3's explicit archived/drained runtime RELEASE at 23:26:55Z preceded allocation. Its provider stop receipt and retained drain evidence were independently read and referenced by exact PATH+HASH. The sole new box was bx_nb2npb7k, returned with TTL 1493 seconds and archiveAfter=2026-11-08T23:54:21.744Z. The service did not return expiresAt. A durable UUID and observable independent immutable 25-minute watchdog were armed before create. The browser deadline was 23:52:21.885Z. No agent, peer WIP copy, RAM gate or public deployment was used.

The runtime uses the published 6e325da67 composition and the unchanged native Pause controller, lifecycle and queued-custody helpers. The staging Git SHA is 3fbc7892ea61666c6d448a64f915f57a5a6b897a; retained runtime providers keep their individual committed-source/media/module selections. The final startup barrier verified 1,386 providers / 61,312,807 bytes. The composed driver SHA is 01ce7377954af22bd32b2eaab49ef0e9bc59b0d86ccb133f7339660e25bb2ec7. Unchanged accepted focused controls and locked build were referenced by PATH+HASH rather than rerun. Source recovery uses Git plus small owned patches, without tree archives, repeated media or executing-module copies.

The new command path retrieves the ACK, original capture metadata and PNG in one remote command, independently checking the PNG SHA locally before review. Actions require exact equality with the locally retrieved prior capture; timestamps, owners, pins, independent UP, actual completion ordering and the 12-second boundary are unchanged. Typical complete capture/retrieval calls took about 1.3 seconds. Fifteen admitted native Pause compositions had admission ages 4,974–8,527 ms, 45 distinct phases and 46 fulfilled DOWN / 46 fulfilled UP controller operations. Receipt snapshots are distinct from phase counts.

An initial owned wrapper resolved its retained script one directory too low. It failed before a supervisor, original claim, Chrome or game existed. Its trace and actual wrapper wait were preserved. The path was corrected and the final barrier republished before the sole actual original. The browser execution window began at 23:31:22.716Z, followed the normal menu/slot/story/map route, and entered Welcome to Antarctica. Optional opening coins were skipped. Ground contact was reviewed before the one admitted jump toward the first pillar. A reviewed continuation landed back on the floor before that pillar.

The final capture began at 23:35:00.120Z. Deliberation over the failed jump and pillar geometry delayed the next proposed action until 23:35:17.761Z: 17,641 ms. The controller correctly refused it as stale before DOWN, with zero gameplay effects, sticky UNKNOWN and no replay. The short transfer path worked; human-equivalent review/reasoning still exceeded the unchanged bound. The published strong UNKNOWN propagation also worked: it produced a terminal failure, rather than a refreshable stale ACK. No newly exposed repository code defect was established, so no production code was changed. The command client waited its existing 30-second ACK bound after the terminal failure; this was not interpreted as permission to send further input.

Closure and evidence limits

Chrome closed normally: close ACK, actual exit 0, signal null, no escalation, terminal plus stdio drained in 12,399 ms, physical pending input zero. The kernel journal records 3,396 events / 325 owned PID/start identities / 325 actual reaps. Before-wait witnesses were checked. Remote parent waits returned 1 and 0, each with stdio EOF; the nonzero supervised result retains the controller failure. Ports 40657/44633, writable FDs, active profile, input lock and runtime lock were drained. CLONE_UNTRACED, unsupported nonleader exec and external-signal limitations remain explicit.

The local launch tool session separately returned 143 with no local wrapper exit receipt or pre-recorded PID/start. Its cause is UNKNOWN; the empty gzip stream is retained and is not substituted for a successful local wrapper wait. The independent remote parent/outer actual wait receipts establish remote terminal completion. A local process observation also matched its own inspection shell text; that match is not evidence of a remaining launch process.

All 308 remote regular files (305 evidence files, three source references) were covered by 247 unique gzip transports / 7,579,654 stored bytes. Each transport was independently reopened and checked against stored/original SHA and size, including nested gzip CRC, before the delegated normal box stop. The box was archived at 23:37:02.517Z, archiveAfter=null, expiresAt NOT RETURNED. Receipt stop_5c6cbbc22531080a completed at 23:37:02.537Z, forced=false, error=null.

Watchdog actual wait was 0, board-tail actual wait -15, both stream threads reached EOF, and the supervision wrapper returned 0. Board events and wrapper logs have distinct filenames and gzip from their first stored byte; the 2301 same-filename corruption did not recur. The unchanged custody kernel initially writes two metadata JSON receipts raw; their exact bytes and compressed recovery are retained, without claiming gzip-first storage for those metadata files. Local free-space samples stayed above 1.5 billion bytes; no continuous-floor claim is made. No peer or old evidence was deleted.

Next work needs a separately authorized original with a simpler reviewed grounded pillar-jump decision that fits 12 seconds. Exit, unlock, full-game playability, audio and FPS remain open. This single task stops here.