SuperTux onward gameplay: blocked before allocation

The requested new coin, question-block, or level-exit consequence was not attempted. /home was below the required 1,500,000,000 free bytes throughout preparation: the initial check returned 1,491,369,984, and a later check returned 1,488,363,520. This task's entire evidence directory was about 0.55 MB, insufficient to recover the deficit. No peer files were removed. Warcraft0244's exact ARCHIVED PHYSICAL_DRAINED release was also still pending. The earlier Q2close0244 release does not satisfy that dependency.

Evidence is in scratch/runs/20261109-supertux-interactive-onward-0251/. This is a concrete pre-allocation blocker, not gameplay success or an emulator defect. No production code changed. No browser, box, original, game input, or capture was started, and there are no new screenshots to inspect. Box ID, expiry and stop receipt are inapplicable because creation was never attempted. The deadline watchdog was deliberately not armed while allocation remained blocked; it must be observably prearmed before any later finite-TTL creation.

Offline preparation selected published providers at Git aa3913efc5b139a68946346a052dcca5bdd0b1e0, retaining the published df0932c1c terminal-failure repair. The fresh canonical barrier passed with 1,481 providers, native observation OFF, and the accepted CPU module hash a320d4c85156644fd12b6134d66b11784f3100b9b135756206c087cdacd43295. Exact singular Enter, ArrowDown and Escape payloads passed the actual composed executor offline. The prepared review helper retains the explicit airborne=true, grounded=false, empty-key 200 ms neutral-settle choice and the unchanged 12-second freshness bound. No route or detector was added.

Accepted unchanged controls and build logs were hash-checked and reused; there was no new build. An initial reuse assertion compared the old fixture manifest with repaired composition bytes and failed. Inspection showed that the final focused test overrides those manifest bytes with the production composition. The final repair-source proof matches current code and df0932c1c; the failed comparison is recorded in accepted-0212-pathhash.json.gz. The fresh exact-menu checks passed separately. Git SHA and small run-input patches preserve preparation without source, media or module archives.

The board watcher was terminated and actually awaited before stopping this worker; its wrapper's separate EOF and wait records remain in the run. The tail child's historical start identity was not recorded and remains UNKNOWN. No runtime lock was acquired. Next work needs restored disk headroom and the exact Warcraft0244 release before the one authorized fresh original can proceed. The accepted first-enemy stomp and floor landings remain prior evidence; the first snowy pillars remain background scenery. No geometry defect is claimed or reopened here.