Maelstrom: one bounded packet-return capture did not reach Sync

Historical source last updated, 2026-10-24. Runtime and implementation claims below describe that dated source; see current app notes and source for subsequent changes.

Exactly one original guest ran on bx_bewteqdp. The unchanged 42,000-batch window ended with zero hits at every requested trace PC; all six counters, including actual Sync entry and afterNextWave, are zero. Therefore no select/CheckSockets/Recv return EAX, current-frame missing-slot state, packet metadata or selected Sync branch was observed. CheckSockets timeout versus positive readiness/rejected packet versus SDL_net internal errno retry remains unresolved. This is the first runtime observation blocker; there is no second guest or extended observation.

The full raw output (historical artifact: maelstrom-sync-packet-return-capture-20261024/output.log), actual argv and execution receipt (historical artifact: maelstrom-sync-packet-return-capture-20261024/command.json), terminal receipt (historical artifact: maelstrom-sync-packet-return-capture-20261024/terminal.json) and analysis (historical artifact: maelstrom-sync-packet-return-capture-20261024/analysis.json) are retained. Final EIP is 0x00417430, final EAX 1; this is not EAX at a requested return. The host process returned zero in 0.632s, and the harness reports 42,000 batches in 0.428s; this does not establish native guest normal exit. There was no trap, denied access, OOM, timeout or output-guard event. The output is all 3897 bytes, with no truncation. All three scheduled captures exist and have identical full hashes; the inspected menu capture is uniform teal. No menu, gameplay, production defect, packet rejection, self-delivery failure or permanent hang is claimed.

Exact inputs and limits

The immutable input was strict-SSH remote verified 6c265033d01e547a3d9320316cc17027bbb7cb0b. The accepted recipe (historical artifact: maelstrom-sync-loop-cause-20261024/capture-recipe.json) was used byte-for-byte in argv after replacing only the old owned allocation path with this task's allocation. This includes the historical hash-gated passive observer preload, P/key schedule, three captures, 200ms clock, 42,000 batches, wall60/CPU90, fixed512MiB linear memory, Node heap512, trace start36163, five exact PCs, 16 records, esp:384,0x41f9d8:128,0x420658:12, <=8384 potential raw memory bytes and actual131072-byte output guard. No observation record was emitted. No errno pointer was read.