SuperTux 0525: personally verified coin consequence

The fresh original achieved meaningful gameplay: after an upward jump-100 beneath the first question block, the personally inspected native PNG showed score 50 → 75 and coins 2 → 3. The original's starting 50/2 was excluded from progress. No first exit or depleted-block state is claimed.

Evidence: scratch/runs/20261109-supertux-prompt-image-jump-0525/. Final native PNG: current.png, 275,648 bytes, SHA-256 7f1bcd242c67600c60a2cb529e3aede20906e6dddc95fef2d2a32f4b8147ee5b, source 2026-11-09T05:33:14.278Z, completed 05:33:14.570Z. Its PNG chunk CRCs and IDAT zlib stream pass. The immediately preceding personally viewed PNG still showed 50/2, with grounded Tux beneath the block. personally-verified-consequence.json.gz records those exact captures.

Read CLAUDE, AGENTS and the 0512 note. That run's first jump had failed before gameplay HTTP because an extra capture-completion poll aged its PNG to 14.051 seconds. This run awaited capture, retrieved and hash-checked the PNG, then returned the image through view_image inside the same functions.exec. There was no separate completion-poll turn before displaying gameplay images. Every live gameplay action was selected only after personally inspecting that fresh PNG. No live route was preselected or looped. The helper required an explicit paused-grounded or paused-airborne declaration for each choice; missing posture had no default. Neither pixels nor the selected action were used as a substitute for personal review. No timestamp was changed.

Before create, the exact prepared helper wrapper and its actual compiled implementation exercised the shipped review page, real HTTP, actual numbered transport and composed executor. Exact jump-right-200 was {"keys":["ArrowRight","Space"],"holdMs":200}; exact jump-100 was {"keys":["Space"],"holdMs":100}. Both and their explicit airborne neutral-settle-200 follow-ups passed, with 22 balanced key events. The first offline display used the existing fixture's synthetic non-PNG bytes and was rejected by the image tool. Only the offline fixture pixel supplier was changed to reference a retained valid PNG; the combined await/retrieve/display check then passed. Retained fixture pixels never authorized native input.

The exact persistent-caller branch also passed offline with its own parent's stdin at EOF: the child's independent pipe remained open through actual wait, with concurrent drains and separate stdout/stderr EOF. Ten prior focused-test, locked-build and custody logs were reopened and matched their recorded SHA-256 and sizes. The unchanged actual eleven-child setup proof is reused by reference. Local preflight and the remote preCPU/pre-DLL-main barrier verified all 1,586 pinned providers. No production code changed.

Composition remains published fddc9322aa42497bedeebfeef6447a47ff0df6e6, SHA-256 3793f2757d4189fed48a5f8ec898e25722cb9c9787429db1387d09345c03a48d; custody remains published 4341b87723a7d56bc98223215cca4cdc878fcae2, SHA-256 d38f2092c7fc0d5b1e4caabf2bd21040167d4f147c55186fd6e4a39cd00a4636; CPU remains a320d4c85156644fd12b6134d66b11784f3100b9b135756206c087cdacd43295. Strict flags and every startup, work, ACK, hold, close and runtime cap remain unchanged, including freshness 12 seconds, aim 8 seconds.

Personally reviewed setup selected Start Game, free Slot 1, story skip, Welcome to Antarctica, first-level entry and native Pause. Loading frames received captures only. Thirteen individually selected gameplay actions followed: five short right jumps with five individually reviewed airborne settles, two short right positioning moves, then the upward block jump. All accepted helpers actually waited 0 with separate output EOF. Their source ages at helper start were 6,865.399–9,141.017 ms; three exceeded the 8-second aim, all remained below the unchanged 12-second cap. The successful block jump's helper age was 7,796.327 ms. Full rows are retained in freshness-helper-audit.json.gz. No later input, capture or retry followed the verified consequence. Deliberate no-input cancellation ended runtime.

Create followed Quake2 sparse-native-combat-0517's exact ARCHIVED PHYSICAL_DRAINED release, stop_cba893c72832a8f4. The independent observable watchdog was armed 05:28:09.737Z, immutable deadline 05:53:09.629Z, UUID 9fdd0c08-b7ad-41d5-be7f-7e120540cdcb, before create. The sole box was bx_rpz4kdec, TTL 1,491 seconds, initial archiveAfter 05:53:09.644Z; expiresAt was not returned. Caller stdin was held through actual wait with concurrent output drains.

Cancellation reaped 371/371 owned identities, 4,095 journal events, complete=true, failure=null, no unresolved lineage, remaining or unreaped identity, and closed command/journal streams. Ports 37663/39041/8787, writable run FDs, input lock, active profile and runtime lock drained. The empty stale review-client lock was removed only after verifying its exact owner was reaped and its port closed. Kernel-parent actual wait was 1, outer actual wait 0, each with separate stdout/stderr EOF; local runtime, watchdog and supervisor actually waited 0. This was cancellation cleanup, not evidence of normal browser-close acceptance. The inherited drain proof's phrase “nonleader exec unsupported” is obsolete; published custody is 4341.

All 450 regular artifacts / 371 unique transports / 6,954,733 stored bytes were recovered or SHA-referenced and independently reopened with external SHA-256, exact sizes and GNU gzip CRC before delegated normal archive. One incomplete nested client-stdout.log.gz remains preserved verbatim, CRC UNKNOWN; its outer transport passes. Outer EOF does not establish nested completion. Stop stop_6966241a5392ff24 completed 05:35:27.161Z, forced=false, error=null, final ARCHIVED, stoppedAt 05:35:27.139Z, archiveAfter=null. Exact PHYSICAL_DRAINED release was posted 05:35:41Z. An extra read-only local boardwatch transport later returned 143; its recorded child identity was already absent and its actual child-wait record was missing. That watcher's actual wait and separate EOF remain UNKNOWN. The separately supervised watchdog and runtime waits above are preserved.

Git base plus small run-input patches, relevant binary diff and parent manifest references preserve source recovery. No source tree, game media or module archive was made. No Q2, WC or custody file was edited; no agent, worker, local browser or deployment was used. Free /home stayed above 1.5 GB; no old run or session was deleted. Only this note is published. The requested consequence is achieved; no further runtime is scheduled. Single task STOP.