SuperTux: actual browser-client jump toward the first pillar

The one authorized original reached the first pillar and performed an actual jump-right-200 through the published e78 browser review page and HTTP endpoint. Its new native Pause frame shows Tux airborne beside the pillar. Landing on the pillar, onward movement after the jump, and the first-level exit remain unverified. This is gameplay evidence, not a preparation-only result or a production repair. No production code changed.

Evidence: scratch/runs/20261109-supertux-correct-key-pillar-0046/.

Before allocation, the exact setup.py start-game key Enter 100 invocation generated its payload through the retained setup source. The actual composed driver's execute and input validators accepted singular key, Enter, ArrowDown and Escape. A plural keys negative control failed before mock input. No native game or original ran during that validation. The live singular menu commands then selected Slot 1, skipped the story with Escape, entered Welcome to Antarctica, and requested native Pause.

For gameplay, a second tab in the same original browser opened the unchanged published e78cb70d2a71853bec4d41392ab62ab46ea946fb review page. The small run helper checked its Pause/ground boxes, supplied my frame-specific review, and clicked its actual capture/choice controls. Its existing JavaScript sent the HTTP requests through the accepted numbered driver transport. The helper never sent game input itself. There were 29 completed gameplay choices: 28 right-100 approaches and one jump-right-200, with a personal review of each new native frame. Controller caps, options, ACK limits and preload order stayed unchanged; native observation stayed OFF.

The jump used grounded capture review-c30d6d79-2789-4ebf-bfb1-aa7e7db3a7c6, originally captured at 01:05:39.052Z. Tux was grounded around x289; the first raised snowy pillar began around x364, with an enemy near its base. The explicit jump choice was recorded at 01:05:46.626Z, age 7,574 ms, meeting the 8-second aim under the unchanged 12-second limit. Other accepted choices reached 10,866 ms; this run does not claim every choice met the early target.

The resulting native capture is review-22aabbdb-267e-4f5e-8edd-fdebac7a8877, at 01:05:47.625Z, SHA-256 6a5f4cc56c7851e26a40a2b9a4662229f281ceab185cad466614aab13b2f8abf. It shows visible Pause, Tux airborne to the left of the first pillar, and the enemy below. It proves the jump and rightward approach, not a landing. Score 50, two coins and four displayed life icons were unchanged. I stopped gameplay because I could not truthfully attest grounding for the next client choice. No airborne bypass, autonomous route, replay, second life or second original was attempted. Continuing needs a separately authorized way to observe landing without falsely confirming ground contact in the existing client.

Two helper calls encountered the browser's disabled choice button before click(), HTTP submission or any input. They did not consume a client token or create a numbered game command. Explicit new screenshot captures preceded the later choices; no frame was retimestamped. Neither the driver's first-failure file, transport-closed file nor review-client UNKNOWN file existed at shutdown. The second refusal occurred before the server's 12-second age because the browser conservatively adds its measured request duration to the age display. These are retained zero-effect UI refusals, not successful choices or repaired defects. Ordinary quit ended the original; no death was observed.

Q2guard-door0046 explicitly released the sole slot at 00:55:47Z as RUNTIME_RELEASE NONE NOT_CREATED DRAINED: it had repaired startup without creating or holding a box, so peer archive/expiry/stop receipt were inapplicable. The interruptible release watcher was stopped and actually awaited after this explicit no-box release. No peer box was accessed.

The full final local and remote canonical barriers matched 1,406 providers / 61,348,759 bytes, manifest SHA-256 778e74b0653118607bebd967a412133cb0425ec59175dd7ad94622c87cfd9084. They used the existing canonical Git-blob resolver and published providers, including the client, with CPU SHA-256 a320d4c85156644fd12b6134d66b11784f3100b9b135756206c087cdacd43295. Accepted unchanged client controls, current-module parity and locked-build receipts were reverified by PATH+HASH and reused. Offline wrapper preamble and syntax failures were corrected before allocation and remain in evidence. Git SHA plus small owned input patches preserve source recovery; there are no source/media/module archives or copied game media in the run evidence.

An independent immutable UUID/deadline watchdog was prearmed before the only create. Deadline 01:21:51.813Z; box bx_ntaeeze7, TTL 1,484 seconds, initial archiveAfter=01:21:51.111Z, expiresAt not returned. The original began at 00:57:50.860Z. Local launch PID 720323, start 223307979, actually waited 0 with stdout/stderr EOF. Remote parent 5868/start7845 and outer 5867/start7836 both actually waited 0 with EOF. Browser.close was ACKed; Chrome exited 0, signal null, normally in 218 ms, without escalation. Review client PID 6060 exited 0 with both streams at EOF.

Custody verified 374 owned identities / 374 actual reaps / 3,944 events, including before-reap PID/start witnesses. Ports 40933, 46783 and 8787, all writable run FDs, profile, writer/client/runtime locks and physical pending input were drained. All 545 remote regular files were accounted for: 537 evidence files and eight pinned source references. 440 unique transports / 14,103,305 stored bytes passed independent original/stored SHA-256, size, GNU gzip CRC, nested CRC and exact-set verification before delegated normal stop.

The box was archived at 01:07:52.099Z; receipt stop_0a145c01e011db1d completed 01:07:52.117Z, forced=false, error=null. Final archiveAfter=null; expiresAt not returned. Watchdog 718742 actually waited 0, tail 718743 waited -15, with streams closed and supervision awaited. Archived/drained release was posted at 01:08:11Z. Historical status-143, nonleader-exec, untraced-clone and external signal UNKNOWN limits remain unchanged. No RAM gate, peer/old deletion, agents, public deployment or runtime left billing idle.