SuperTux 0400: validated Enter caller and bounded client gameplay
Evidence: scratch/runs/20261109-supertux-validated-enter-gameplay-0400/.
The requested new coin/block/exit consequence was not achieved. The one
authorized original reached the world map. My next setup action, map-down,
failed terminal admission at 04:08:56.668Z. Its personally inspected source
capture was timestamped 04:08:44.559Z, making it 12,109 ms old at the
failure, beyond the unchanged 12,000 ms freshness cap. I did not meet the
8-second aim. The retained wrapper reports native menu action UNKNOWN; its
inner cause is not preserved, so stale refusal is consistent with the timing,
not an independently retained original exception. There is no admission or
pulse record for map-down. No retry, later input or capture followed. Native
Pause, review-client startup, explicit initial client capture and gameplay
choice were not reached. No production code changed.
Before allocation, offline.py generates the exact setup helper JavaScript for
ten capture/key/Pause setup commands. Each runs in an actual Node child through
published requestReady, real numbered transport, and the composed production
execute function. Only capture pixels, identity admission and CDP effects are
offline boundaries. The real input validator and pulse execute; Enter,
ArrowDown and Escape yield six balanced DOWN/UP pairs. The initial capture
request creates neither command nor writer lock before readiness. All ten
children terminate 0 with separate stdout/stderr EOF. The negative Return
spelling fails ordinary-key validation before admission. Supported production
actions are capture, click, key, pause-step and quit; key is singular.
The first offline fixture omitted the production JSON storage adapter and could not read its caller's compressed review record. Its failed directory and stderr are retained; a fresh fixture with that adapter passes. No original or browser ran in either fixture. This is a fixture correction, not a production repair or native gameplay acceptance.
The exact composition SHA is
6415f8ff63c0e8fa8bf0ffb6cd484021059192bd285f6f4f28dcfbe4c5d8d4fc.
Published readiness latch 7df56770a, custody
2df8d81b41da78ac0ab846137cf4137f0f1c4a86, and CPU
a320d4c85156644fd12b6134d66b11784f3100b9b135756206c087cdacd43295
remain pinned. Super0335 focused checks and locked build were independently
reopened and matched to their recorded SHA and size; unchanged tests/build are
reused. Observation is OFF; runtime, startup, input and 12-second review caps
are unchanged. Setup captures provide no review-client token. Git plus small
run-input patches supplies source recovery; no source/media/module archive.
The final precreate manifest verified 1,530 files / 61,578,209 bytes, SHA
9b3033cf7cdd608b11453fc813b2355841387d21ef328843af72b95575c6e7f8.
Q20350's exact bx_nckcav9a, UUID
48092a8d-d338-4d68-abf2-9cdfd6566b9d, initial expiry 04:20:53.729Z
was bound to its explicit ARCHIVED PHYSICAL_DRAINED release at 04:05:47Z,
receipt stop_eabd003c16a8aaa7, before allocation. Independent watchdog UUID
0469eedf-c689-4be5-b575-85c668d80663 was observable before finite-TTL creation;
its immutable 25-minute deadline was 04:30:56.575608Z. The sole new box
bx_ee97uv9k had TTL 1,494 seconds, initial
archiveAfter=04:30:56.575Z; expiresAt was not returned. Provisioning rechecked
the same complete manifest remotely. Driver readiness preceded the first setup
request, and every helper used requestReady, never a legacy queue.
I personally inspected all seven requested setup PNGs. Accepted ordinary Enter
opened Start Game and confirmed highlighted Slot 1; Escape skipped the story.
The final world-map PNG already shows score 75, coins 3, before any new
level gameplay; these values are not a newly demonstrated consequence. Their
prior provenance was not established here. Its explicit local path is
scratch/runs/20261109-supertux-validated-enter-gameplay-0400/current.png, SHA
76611a395c2714a2b8541735021cc2f52cb3f12e5aea79c38ee4045e090c19f8.
The original compressed capture is review/world-view.png.gz in the same run.
No background pillar was treated as collision evidence.
The first terminal failure closed the session. Explicit no-input SIGTERM cancellation of the exact kernel supervisor identity produced launcher wait -9, kernel parent wait 1, and outer parent wait 0, each with separate stdout/stderr EOF. This is forced process cleanup, not normal browser-close acceptance. The browser-close journal contains an ACK before cancellation; that does not establish normal browser terminal completion. Kernel custody retained 219 owned identities / 219 actual reaps / 2,146 events, complete=true, with before-wait witnesses and no unresolved lineage, remaining identities or unreaped children. Ports 39687/33347, writable run FDs, input lock, active profile and runtime lock drained. The reused drain proof's static “nonleader exec unsupported” label is obsolete; actual custody was the pinned published 2df8 version. No historical UNKNOWN was resolved.
Recovered 148 regular files / 113 unique transports / 2,071,537 stored bytes.
Original/stored SHA and sizes, independent reopen, GNU gzip CRC and exact-set
checks passed before delegated normal box archive. Stop receipt
stop_ada7e0a05149d0d9 completed 04:09:44.400Z, forced=false, error=null;
stoppedAt=04:09:44.383Z, final state ARCHIVED, archiveAfter=null.
Physical drain was posted at 04:10:03Z. Local runtime and watchdog-supervisor
wrappers actually waited 0, watchdog 0, and board tail -15, retaining
separate stdout/stderr EOF. Archive success does not establish normal browser
shutdown.
Free /home stayed above 1.5 GB. No agents, workers, local browser, peer-box operations, RAM gate or public deployment. Full27/parity/audio/FPS remain open. Next requires a separately authorized original and promptly chosen setup actions as well as explicit native-Pause client capture/inspection/choice; no deadline extension, replay or automatic route is authorized. This single task stops.