SuperTux 0512: jump paths proven offline; first live choice expired
Evidence: scratch/runs/20261109-supertux-native-block-jump-0512/.
Meaningful gameplay was not achieved. The first live jump-right-200
helper refused its expired source image before gameplay HTTP submission.
This was my operator delay, not an established SuperTux production defect.
The assignment ended at this first failure, with no later input, capture or
retry. No production code changed.
Read CLAUDE/AGENTS and the 0455 handoff, personally inspected its retained
PNG, and read the actual client enumeration. Before create, the exact prepared
helper wrapper and its actual compiled implementation exercised the shipped
review page in a DOM/CDP fixture, real HTTP, actual numbered transport and
actual composed executor. jump-right-200 is precisely
{"keys":["ArrowRight","Space"],"holdMs":200}; jump-100 is
{"keys":["Space"],"holdMs":100}. Both and their explicit airborne
neutral-settle-200 follow-ups passed, with 22 balanced key events. Fixture
pixels and asserted fixture grounding are not native gameplay evidence.
The exact persistent-caller branch also passed offline while its own parent's stdin was EOF: the child's independent pipe remained open through actual wait, with separate stdout/stderr EOF. Ten prior focused-test/build logs were independently reopened and matched their recorded SHA-256 and sizes. The 0415 locked build and 0420 custody suite/build are reused; the unchanged eleven-child actual setup proof from 0445/0455 is retained by reference. Current preflight validated all 1,584 pinned providers. The final remote preCPU/pre-DLL-main barrier matched the exact local closure and was required before launch.
Published composition remains
3793f2757d4189fed48a5f8ec898e25722cb9c9787429db1387d09345c03a48d
from fddc9322aa42497bedeebfeef6447a47ff0df6e6; custody remains
d38f2092c7fc0d5b1e4caabf2bd21040167d4f147c55186fd6e4a39cd00a4636
from 4341b87723a7d56bc98223215cca4cdc878fcae2; CPU remains
a320d4c85156644fd12b6134d66b11784f3100b9b135756206c087cdacd43295.
Strict flags and all startup, ACK, hold, close and runtime caps are unchanged,
including freshness 12 seconds and aim 8 seconds. No retimestamp, detector,
autoroute, forced attestation or bypass was introduced.
Observed Super0455's exact ARCHIVED PHYSICAL_DRAINED release before create.
The independent immutable watchdog was visibly armed at 05:12:00.356Z,
UUID 6b5471f9-14eb-4bed-84bc-b87467925896, deadline
05:37:00.292Z. The sole box was bx_sqfc9g5t, TTL 1,493 seconds,
initial archiveAfter=05:36:59.825Z; expiresAt was not returned.
The remote caller pipe was armed 05:12:59.870374Z, before child launch,
and retained through actual wait with concurrent output drains.
Each setup input followed personal inspection of the freshest PNG: Start Game, free Slot 1, visible story skip, map node Welcome to Antarctica, level entry, and native Pause. Explicit captures observed loading transitions. This original's baseline was score 50 / coins 2, excluded from progress. The personally viewed initial client PNG showed native Pause, Tux grounded at x≈146/y≈640, continuous snow to the right, and the first question block centered x≈432. I chose the enumerated grounded jump toward that block.
The source PNG was produced 05:15:15.761Z, completed 05:15:15.941Z,
SHA-256 4f89afc15ea3b56756fc6424a7f0849faf0bb6d3a2fcc114683b2c9b29724bae.
The remote transport started 05:15:29.794Z (source age 14,033 ms);
the actual Node helper started 05:15:29.812280Z (age 14,051.280 ms),
and actually waited status 1 at 05:15:29.852418Z, with separate output EOF.
Its CDP exception was Error: review choice disabled. The source exceeded
the unchanged 12-second cap before the button click. The original numbered
queue has exactly twelve setup/capture commands, no pause-step; the kernel
command log ends at the initial client capture. Thus no live jump or neutral
settle was submitted. The extra completion-poll round trip before displaying
the PNG consumed freshness; future orchestration should await capture and
display its PNG in the same tool call, without changing the cap. Historical
0400's cause remains UNKNOWN.
No-input cancellation reaped 267 / 267 owned identities, 2,980 events, complete=true, with no unresolved lineage, remaining or unreaped identity and closed command/journal streams. The launcher exit was -9 during cleanup; kernel-parent actual wait was 1, outer actual wait 0, separately from stdout/stderr EOF. This is cancellation cleanup, not normal Chrome-close acceptance. Ports 35251 / 37733 / 8787, writable run FDs, input lock, active profile and runtime lock drained. An empty stale review-client lock was removed only after its exact owner was verified reaped and port 8787 closed. The initial drain refusal and an incorrect gzip-only cleanup reader invocation are preserved; the corrected magic-aware reader passed. The inherited drain-proof phrase “nonleader exec unsupported” is obsolete; the actual custody provider is pinned published 4341.
All 230 regular artifacts / 186 unique transports / 3,352,942 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 verbatim, CRC UNKNOWN;
its outer transport CRC passes. Outer EOF does not prove nested completion.
Stop stop_a75a6c7dd9ff1c8c completed 05:17:30.895Z, forced=false,
error=null, final ARCHIVED, stoppedAt=05:17:30.844Z, archiveAfter=null.
The exact PHYSICAL_DRAINED release was posted 05:17:45Z, allowing WC0512
to proceed. Local runtime, watchdog and supervisor actually waited 0; the
supervised board tail waited -15, with separate EOF recorded.
Git base plus small run-input/owned-note patches and provider/media path+SHA references preserve recovery. No source tree, media or module archive was created. No agent, worker, local browser or deployment was used. Free /home remained above 1.5 GB; no old run or session was deleted. Only this note is published. Next runtime requires a separately authorized fresh assignment; this single task is stopped.