SuperTux current manual platform/course admission, 2026-11-18
No original was launched. Platform/course progress and ordinary Quit remain
unproved in this task. The actual /home free space fell below the owner's
1,500,000,000-byte floor during read-only preparation: 1,499,611,136 bytes,
then 1,499,041,792 bytes at the retained admission audit. No runtime scope,
endpoint, input owner, DOWN, native watchdog or browser was created. This is
a storage launch refusal, not a guest/controller UNKNOWN or a SuperTux defect.
No foreign files were removed and no storage cause is inferred.
Evidence: scratch/runs/20261118-supertux-current-manual-platform-course/.
The run contains the admission, original-media verification, retained-module
audit, exact Git and relevant binary diff, recovery instructions, and explicit
null native-exit/wait records. result.json is written last.
The registered original remains supertux_013, with --sdl --datadir data.
Read-only node tools/verify-supertux-013.js passed: all 787 original payload
files, authentic CRT and all 786 companion manifest mappings. All 789 pins
from 20261114-supertux-early-platform/media-pins.json still match. No media,
settings, saves, clock or game state was edited or used to select movement.
The retained native SDL candidate module in
20261118-lmarbles-connected-send-freshness-repair-puzzle8/tested.wasm.gz
decompresses to SHA-256
0d383140f6d4207d18860e3cb22fc8fcc47a5d260b8d5f2443222396b245fdd5,
matching its recorded module identity. All 251 recorded runtime source
pins match the current files. This establishes a recoverable candidate graph;
it does not qualify a new SuperTux run. No unchanged WAT compilation, module
copy, source snapshot, browser startup or original retry occurred.
Both requested route notes were read. Their earlier selected images, counters, deaths and ordinary-Quit outcomes remain separate and untouched. The pit-route run died at the second row after a late launch; the early-platform run died during its approach before submitting that jump. Neither establishes a physics defect or a successful pit crossing. This task adds no gameplay evidence and makes no new jump/landing claim.
There was no code repair justified by this admission failure. Common helpers,
LMarbles/ReVolt/SDK ownership, foreign WIP, Heroes II and security holds were
left untouched. The sole tracked change is this report; validation consists
of the read-only inventory/provenance audit and report whitespace check.
No workers, boxes, Python, Wine or deployment were used. Box ID null, state
NOT_CREATED, expiry null, stop receipt null. Native exit, actual native waits
and ordinary Quit are explicitly absent because no original process existed.
The worker releases ownership and stops. A future authorized scope still needs the existing disk floor satisfied before qualifying the native input path and personally reviewing finite movement toward the early row and pit.