SuperTux wall-time: new coin consequence, then review-expiry stop

Evidence: scratch/runs/20261114-supertux-wall-time-consequence/.

One separately authorized fresh local standard CLI original used the existing --real-ticks switch. It achieved a new coin consequence beyond its actual fresh baseline. Native menu Quit and level exit were not achieved. The next choice failed the unchanged 12-second review guard before input submission; first-failure termination ended this assignment. No retry or replay followed. The predecessor default service-clock TIME’S UP record remains unchanged.

Original identity and selected clock

Launch HEAD was 1dcd68cf86003d5622a8f54d14141712c0b97db2; loaded module SHA-256 dcf6e8f0ca9d361c10fa556fb30835d34cf5bfe4089f84d298cb57fd170dbd42. Exact 317 source pins, foreign uncommitted hunks and the new controller are recorded as hashes and Git patches. Postflight found zero source/module/media drift. No source-tree archive or media copy was made.

Filesystem verification passed all 787 originals (16,107,101 bytes), all 786 companion manifest mappings and authentic standing MSVCRT. EXE 792,576 bytes: 5930d9848beec72fcaea0687d745e1c9fc148245abbf3f856c208ed41d83265c; manifest 119,228 bytes: fe8e477d912c25a4d6542a9ee2eb706e002a61123b3f425814a810d4009ae3bc. The actual registered route selects guest cwd C:\ and --sdl --datadir data. The native log confirms the six bundled SDL/image/mixer/jpeg/png/zlib DLLs and standing CRT mapped, with successful initializers. No original sound, settings, bindings, profile, physics, score or timer-state edit occurred.

launch.json records --real-ticks; actual native trace says clock=real. Before gameplay, title-ready to Keyboard Setup advanced 51,677 guest ms in 51,677.272558 wall ms. clock-observation.json records the interval. Its first parsing attempt selected a trace line without guest-ms; the corrected read-only parser uses the explicit PNG log entry. No clock/deadline change was made to the active process. The prior default-clock result is not passed retrospectively.

Reviewed route and new consequence

Personally reviewed Options retained Sound and Music enabled. Keyboard Setup showed Jump = Space, Power/Run = Left Control, arrows for movement. Ordinary menu navigation selected Start Game, Slot 1 — Free, the visible story (skipped with Escape), world map, first red Welcome to Antarctica node, and Enter. Some immediate post-input captures preceded the visible transition; later explicit captures observed the completed transition without replay.

This run's map and actual first-level baseline were score 100 / coins 4 / four lives. level-loading.png, despite its name, is the reviewed actual fresh level, with timer 297 and Tux near x115. Those counters are excluded from progress, as are historical 75/3 and 125/5 screens.

Three finite Right pulses (700, 300 and 150 ms), each independently released, moved Tux toward the first question block while the camera scrolled. Reviewed align-block.png places grounded Tux beneath its edge. The next reviewed Space pulse, 300 ms, produced score 125 / coins 5, retained in jump-block.png and block-consequence.png. This is +25 score / +1 coin relative to this original's fresh 100/4 baseline. It is a new consequence, even though the totals happen to match a historical baseline. No airborne pose or used-block tile transition was captured; the evidence supports the coin consequence after jumping beneath the block, without claiming those unsampled details. No enemy consequence or level exit is established.

I then spent too long preparing the next choice. advance-jump was rejected locally by review expired before reservation, DOWN, release child or gameplay HTTP. No later input/capture or replay occurred. This is an operator freshness failure, not an established production defect. The run stopped at that failure; there is no reviewed native menu Quit.

Guards, shutdown and validation limits

One permanent input owner, unique nonces, the 12-second freshness cap, immutable finite deadlines, independently prearmed UP processes and postrelease batch progress remained in force. All 22 completed pulses have CONSUMED receipts, successful independent release, actual release-child wait 0 with separate stdout/stderr EOF, and later batch progress.

The independent fixed 600-second deadline watchdog was observably armed before launch. No bound extension or watchdog firing occurred. After the freshness rejection, cancellation sent SIGTERM to the exact native process group after verifying its Linux start token. The native log records orderly SIGTERM shutdown and final statistics at 270.256 seconds; this is cancellation, not native Quit. The outer execution actually ended 143, and the local supervisor disappeared before writing native/watchdog wait receipts. Those individual waits and separate EOFs remain UNKNOWN, not inferred from the native log or process absence. The orphan watchdog was given the controller's completion marker and independently observed absent. All 25 recorded owned runtime/release identities are absent, control port/process gone and heavy lock released. No additional original runtime is authorized by this note.

Current full build passed under heavy-runtime plus build locks; the actual shared-WASM owner test and all 22 guarded CLI checks passed. Four run-local controller checks passed. Offline controls execute the current CLI selector and actual guest-clock implementation: real-ticks disables service time and synthetic wall/guest deltas agree. Synthetic checks are not gameplay proof. An initial test command used a nonexistent guard-test filename; the corrected actual test passed, then passed again under the heavy lock with a clean log. These preparation corrections are retained explicitly.

Twelve selected personally viewed PNGs remain, with CRC, inflate, SHA-256 and size checks; excluded startup/transition captures retain metadata only. Compact logs, JSON and Git patches identify the run. No boxes, remote provider attempts, downloads or deployment. Box ID none; state NOT_CREATED; expiry null; stop receipt not applicable.

Next requires a separately authorized fresh attempt with prompt image review and a supervisor that reliably retains actual native/watchdog waits through cancellation. The current task stops with the verified new coin consequence, operator-expiry limitation and missing shutdown receipts; no semantic repair or broader gameplay completion is claimed.