SuperTux 0445: first level and native Pause, no new consequence
The requested meaningful native level progress was not achieved. One fresh
original reached Welcome to Antarctica and native Pause. The review client
started and its explicit initial PNG was personally inspected. My first client
choice used unsupported right-200; the published walking choice is
right-100. The actual browser page rejected it with Error: unknown explicit choice before clicking a choice or submitting gameplay HTTP. This is an
operator invocation error, not evidence of a production input defect. The live
first-failure rule ended the run: no retry, later game input or capture followed.
No code repair was justified and no second original was created.
Evidence: scratch/runs/20261109-supertux-native-progress-0445/.
Recovery uses source-base.txt, source-recovery.json.gz, small owned input
patches and the exact provider manifest. Git is the source archive; no source,
media or module archives were made. No Q2, Warcraft or custody files changed.
The 0435, 0415 and 0400 notes were read. The owner's explicit NOT_CREATED /
PHYSICAL_DRAINED override was used as the free-slot prerequisite. The original
0435 preparation, eleven-child menu validation, diagnostics and persistent
caller proof were reused. All ten focused/build logs were independently reopened
and matched to their recorded SHA-256 and size, including the accepted 0415
locked build and 0420 custody tests/build. New preflight and remote startup
barrier passed: 1,547 providers / 61,618,942 bytes. The extra providers are
small run inputs. SuperTux remains pinned to published
fddc9322aa42497bedeebfeef6447a47ff0df6e6, composed SHA
3793f2757d4189fed48a5f8ec898e25722cb9c9787429db1387d09345c03a48d;
custody to 4341b87723a7d56bc98223215cca4cdc878fcae2, SHA
d38f2092c7fc0d5b1e4caabf2bd21040167d4f147c55186fd6e4a39cd00a4636;
CPU SHA a320d4c85156644fd12b6134d66b11784f3100b9b135756206c087cdacd43295.
Strict Chrome flags, all caps and the 12-second freshness cap / 8-second aim
were unchanged. No retimestamp, autoroute, replay or bypass was used.
The independent, observable watchdog was armed at 04:43:16.652Z, before
finite-TTL create, with immutable UUID
f5d9d542-b3f4-45f3-b898-43d04545a19f and 25-minute deadline
05:08:16.514Z. The box was bx_66fe2jz2, TTL 1,494 seconds, initial
archiveAfter=05:08:16.469Z; expiresAt was not returned. The remote caller's
persistent stdin pipe was armed at 04:43:57.268Z, before child launch at
04:43:57.269Z, and held through actual wait. Readiness preceded setup admission.
Every setup input followed personal inspection of its latest PNG: Enter selected Start Game and Slot 1; Escape skipped the story; ArrowDown selected Welcome to Antarctica; Enter opened the first level; Escape opened native Pause. Intermediate Loading/menu-transition frames prompted explicit captures, not repeated input. The fresh map already showed score 125 / coins 5; those are baseline, not new progress. The level's starting snow floor, Tux and first question blocks were visible. The native Pause and initial client capture retained the same HUD. No new coin, block effect, exit, death or level completion was demonstrated.
The exact first failing helper started 04:46:49.472Z and finished
04:46:49.588Z. Its personally reviewed client capture was produced at
04:46:39.534Z, completed 04:46:39.746Z, SHA
ab93f68fec8f4faa05ca488d1be119f6becbfb26734fd6b9ecc4555315cc068f.
The helper began 9,938 ms after capture production: below the unchanged cap,
but outside the 8-second aim. The positive exception is the unsupported choice;
no stale refusal was established. The CDP exception, script location, helper
actual wait and separate output EOF are preserved in
client-right-01-boat.stdout.log.gz. The production numbered action was never
submitted, so there is no production action-admission/pulse timing or terminal
failure record for this choice. Local first-runtime-failure.json.gz records
the stop decision without inventing those missing stages. Historical 0400's
cause remains UNKNOWN. Last personally reviewed PNG: current.png in this run;
original compressed image and metadata are retained under review/ and recovery.
No-input SIGTERM cancellation of the exact kernel-supervisor identity drained
274 owned identities / 274 actual reaps / 3,022 events, complete=true,
with no remaining, unreaped or unresolved lineage. Launcher wait was -9,
kernel parent wait 1, outer parent wait 0, with separate stdout/stderr
EOF. This is forced process cleanup, not normal Chrome-close acceptance. Ports
40487 / 41339 / 8787, writable run FDs, input lock, active profile and runtime
lock drained. The stale empty review-client.lock directory was preserved by
rename only after all exact custody identities were absent and port 8787 was
closed. Initial drain assertions and two cleanup-helper invocation errors remain
in evidence; corrected no-input cleanup completed in this same task. The reused
drain proof's static “nonleader exec unsupported” label is obsolete; the actual
custody provider is the pinned published 4341 implementation.
227 regular artifacts / 186 unique transports / 3,560,197 stored bytes were
retrieved and independently reopened, checked with SHA-256, exact sizes and GNU
gzip CRC before delegated normal archive. Incomplete nested original gzip
streams from forced shutdown remain verbatim with UNKNOWN CRC annotations;
their outer transport CRCs pass. Stop stop_e331eb7c272234de completed
04:48:48.139Z, forced=false, error=null, final ARCHIVED,
stoppedAt=04:48:48.116Z, archiveAfter=null. PHYSICAL_DRAINED and the exact
receipt were posted promptly for WC0445. Local runtime, watchdog and supervisor
actually waited 0; board tail waited -15, all with separate stdout/stderr EOF.
Free /home remained above 1.5 GB. No agents, workers, peer-box operations, RAM gate
or public deployment. Only this note is published. Next would require a separate
fresh runtime assignment using the client's enumerated right-100 choice and
prompt inspection/submission; this single task stops after publication.