SuperTux 0542: first failure before gameplay

The requested progress beyond the first question-block row was not achieved. The sole fresh runtime failed at 2026-11-09T05:55:52.741Z with CDP UNKNOWN Debugger.enable; no replay, before readiness or any gameplay PNG. The retained native-input record is empty. No later input, capture, or runtime retry followed; only read-only evidence retrieval and no-input cleanup occurred. The timeout alone does not establish its underlying cause. No production fix was justified or made.

Evidence: scratch/runs/20261109-supertux-beyond-first-blocks-0542/. Remote originals are indexed by remote-inventory.json.gz; unique transports are retained in retrieved/. The original browser failure, browser version, close receipt, kernel journal, process identities and actual waits are retained.

Read CLAUDE, AGENTS and the 0525 note; personally inspected 0525's final native PNG, SHA-256 7f1bcd242c67600c60a2cb529e3aede20906e6dddc95fef2d2a32f4b8147ee5b. It shows score 75, three coins, and airborne Tux beneath the first question-block row. That historical coin consequence was explicitly excluded from this task's success condition. No historical or fixture image authorized native input.

Before create, the prepared wrapper and its actual compiled helper passed jump-right-200 (ArrowRight+Space, 200 ms), jump-100 (Space, 100 ms), and explicit airborne neutral-settle-200 through the shipped review page, real HTTP, numbered transport and composed executor: 22 balanced key events. The offline capture was awaited, retrieved and displayed as a PNG within the same functions.exec; no separate capture-completion polling turn intervened. Explicit reviewed posture has no default; there is no preselected live route, forced attestation, timestamp replacement or freshness bypass. This orchestration was prepared for live decisions, but the first runtime failure prevented its use.

The exact persistent-caller branch also passed with its own parent's stdin at EOF: the child's independent pipe remained open through actual wait, with concurrent stdout/stderr drains and separate EOF. Ten retained focused-test, locked-build and custody logs were reopened and matched their recorded SHA-256 and sizes. Setup validation was reused by hash/reference. Local preflight and the remote preCPU/pre-DLL-main staging barrier verified 1,586 providers.

Pinned composition remains published fddc9322aa42497bedeebfeef6447a47ff0df6e6, SHA-256 3793f2757d4189fed48a5f8ec898e25722cb9c9787429db1387d09345c03a48d; custody remains published 4341b87723a7d56bc98223215cca4cdc878fcae2; CPU remains a320d4c85156644fd12b6134d66b11784f3100b9b135756206c087cdacd43295. Strict flags and startup, work, ACK, close and hold caps were unchanged, including freshness 12 seconds, aim 8 seconds. Concurrent Warcraft custody edits were excluded by the published provider pins.

Create followed Quake2 shattered-pane-onward-0537's exact ARCHIVED PHYSICAL_DRAINED release, stop_e280fc7496b4f011. The observable independent watchdog was armed 05:54:02.220Z, immutable deadline 06:19:02.220Z, UUID bba1a203-ad09-4c2b-ba1f-2c30417f1112, before create. The sole box was bx_bvzvzkmg, TTL 1,493 seconds, initial archiveAfter 06:19:01.863Z; expiresAt was not returned.

Chrome/151.0.7922.108 exposed an endpoint and returned its browser version, then Debugger.enable timed out. The driver initiated terminal cleanup. Browser.close received ACK; Chrome actually exited 0, streams drained, normal=true, no signals, 19,025 ms within the unchanged 30,000 ms cap. Custody recorded 133/133 actual reaps, 1,177 journal events, complete=true, no unresolved lineage, remaining or unreaped identities, and closed command/journal streams. Ports 37765/33739/8787, writable run FDs, input lock, active profile and runtime lock drained. Kernel-parent actual wait was 1, outer actual wait 0, each with separate stdout/stderr EOF. Local runtime, watchdog and supervisor actually waited 0; the boardwatch tail was terminated and actually waited -15, with separate EOF. The inherited drain proof's “nonleader exec unsupported” phrase is obsolete; the pinned custody is 4341. No missing wait was inferred from absence.

All 59 regular artifacts / 37 unique transports / 116,630 stored bytes were recovered or SHA-referenced and independently reopened with external SHA-256, exact sizes and GNU gzip CRC before delegated normal archive. Stop stop_5684743e5f0bb8aa completed 05:57:00.311Z, forced=false, error=null; final state ARCHIVED, stoppedAt 05:57:00.293Z, archiveAfter=null. PHYSICAL_DRAINED release was posted 05:57:16Z.

Git base ea2cf651c80ec7a7c31b7ebc9efd361f02cdc661, relevant binary diff, owned small-input patch and parent manifests preserve source recovery. No source archive, game-media copy or duplicate module was made. No Q2, Warcraft or custody file was edited; 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 work would be offline diagnosis of the Debugger.enable timeout; no further runtime is scheduled. Single task STOP.