Local SuperTux 0.1.3 registration

supertux_013 is a localhost candidate and CLI app, absent from the public desktop. Its original six DLLs are explicit load seeds; authentic corpus MSVCRT is a seventh seed. The original executable runs from c:\ with --sdl --datadir data, with all assets mounted at their original relative paths. No original file is edited and sound is not disabled.

Recover the installer and extraction using the source notes. The observed installer SHA256 is bc4893dbb84a02beb8958dab1c922a7f715aa08ed463d2a0efa6bc58d79c9a9b. Stage its extracted/app directory as test/binaries/candidates/supertux-013/game (copy only into a new destination). Keep the retained extraction evidence intact. Then generate the ordinary ignored local manifest and verify the exact original tree:

node tools/fetch-candidate-corpus.js --id=supertux-013 --prepare
node tools/verify-supertux-013.js

The verifier rejects changed, additional or missing payload files, symlinks, incorrect CRT bytes and incomplete/misdirected manifest entries. Its compact inventory digest represents all 787 path/size/SHA256 rows from the retained scratch/runs/20261018-supertux-source/inventory.json; no second large tracked manifest is needed. The generated manifest contains 786 companions because the app registry supplies the executable separately. The default CRT path is test/binaries/dlls/msvcrt.dll, SHA256 887eb5ce93edb7192ca3e9220f07f9ca0f94db02af5862ebcbdfcb852db99fd1. The verifier accepts alternate fixture-root and CRT paths as its two arguments. It does not fetch, build or execute anything.

After a separately coordinated runtime grant, the registered launch is:

node test/run.js --app=supertux_013 --no-build --wasm=/absolute/pinned.wasm --quiet-api --max-seconds=60 --max-batches=100000 --batch-size=200000

Use a fresh evidence directory and the existing owned-process/disk/log guards. The initial registration had source/filesystem verification only; the bounded registered startup below subsequently validated its menu. The original direct route reached the first level and reviewed ordinary left/right response in 20261018-supertux-gameplay. Timeout/respawn interrupted that initial idle comparison. The registered follow-up below establishes short left/right and jump response; sustained controls, browser/touch delivery, audio and FPS remain unqualified. No public release or deployment is part of this registration.

Registered startup validation, 2026-10-18

scratch/runs/20261018-supertux-registered-startup records the granted 60-second cooperative CLI run of --app=supertux_013, source 83bbb77fdf7b9823359bdf8c927a02f2e878b34b, canonical module SHA256 a4a4bc6aef0f50a191d83acdd0857ff390537701adc381d81436845f20b969e3. There was no build, browser or gameplay input. The log confirms all seven actual DLL mappings. Personally reviewed sample-0.png and final.png show Start Game, Bonus Levels, Options, Level Editor, Credits and Quit.

Unlike the earlier direct route's C:\SUPERTUX, the registry places the executable and relative assets at C:\. Shared resolver replay verified all seven DLL hashes and all 787 original relative paths/bytes. This run validates that absolute relocation through main-menu startup only. The integration checkout also needed the ordinary binaries -> test/binaries symlink for the explicit corpus CRT seed; no differing file was overwritten.

Child 2227625 exited 0 without signal at 17:22:55.091Z after 60.192 seconds; controller 2227610 exited 0. Independent postflight and a separate process check found both absent and no owned process-group survivors. All 3,119 source/runtime pins, 787 retained original files and registered fixture/CRT verification remained unchanged. Minimum sampled free disk was 3,227,095,040 bytes and log output 1,102,473 bytes; no guard fired. The evidence record is reviewed, with no missing/invalid artifacts. The repository-wide evidence checker still reports only the unrelated historical Zuma containment error. This run established startup only.

Registered ordinary gameplay, 2026-10-18 17:31–17:34Z

Evidence: scratch/runs/20261018-supertux-registered-gameplay, source c5cc60ccaafd04e7da99a7b71a4d2b9c8b61321a, same canonical module a4a4bc6a…. This separately granted run used the existing documented --real-ticks option, cooperative --no-threads, batch size 200,000, 180-second guest wall guard, 185-second soft quit and 210-second hard guard. The clock reads elapsed host time; no emulator code, frame cap, time scale, mid-run clock setting or game configuration was changed.

The original README says controls are configurable but gives no jump binding. Ordinary Options → Keyboard setup showed Jump Space, left/right cursor keys, Duck Down cursor and Power/Run Left Control (keyboard-binding.png). Esc returned to the menu. Start Game → Slot 1 showed the story; ordinary Esc skipped it, then Down selected “Welcome to Antarctica” and Enter entered the actual level. Transitional menu/story captures are retained, not labelled gameplay. No settings were edited.

Thirty frames were personally reviewed. On fixed starting scenery, idle Tux is near x115 at TIME 298 and remains there in right-before at TIME 293. A balanced 200 ms Right hold moves him to approximately x127 held, x142 released, and x160 after settling. Left-before still shows x160 at TIME 280; a balanced 200 ms Left hold turns him and moves him to x132 released, then x115 after settling. Space was sent only after reviewing its binding: level-jump-before.png is grounded at x115, held and released images show Tux airborne above the same ground, and jump-landed.png shows him grounded again at x115. Final TIME 259, score 50, coins 2 and four lives establish a same-life sequence without the earlier timeout/respawn confound.

All 24 host keydown/keyup pairs balanced, with independent release timers of 100–200 ms; no key remained held. These times record publication to the CLI, not individual guest acknowledgments. The visible changes support short directional and jump response, not immediate stopping (there is release drift), full-game completion or measured performance. review.json names the exact reviewed frames and limitations; 143 artifact hashes preserve the run packet.

Normal quit was published at 17:34:27.104Z. Child 2236810 exited 0 without signal at 17:34:27.152Z, 179.846 seconds after spawn; controller 2236769 also exited 0. Both were independently absent, owned group empty, all 3,119 source/runtime pins and 787 originals unchanged, registered fixture/CRT verifier passing. Minimum sampled free disk was 2,889,388,032 bytes and log output 1,100,808 bytes; no guard fired. No build or browser was run. Evidence checker has no missing/invalid records and only the historical Zuma error.