Original Penguin visible-projectile attempt, 2026-10-27
Historical source last updated, 2026-10-27. Runtime and implementation claims below describe that dated source; see current app notes and source for subsequent changes.
Visible-projectile acceptance remains OPEN. Both full 840×660 PNGs were visually inspected: the before frame is batch39999; the earliest after frame is batch40060. They show the actual original game field and changed incoming green lines/city explosions, but no distinct A-fired projectile can be identified. This is not evidence that no projectile appeared between captures. No second run, forced state, production change, build, broad diagnostic trace or synthetic gameplay was used.
The actual original-game A keydown was scheduled40000 and dispatched through DispatchMessageA at40033: hwnd10001, msg100, wParam41, lParam1e0001. Keyup scheduled40200 dispatched40295, msg101/lParamc01e0001. The finite six-entry trace corroborates count0→1 and effective cannon ammo10→9 at406ec4/406ed8/406efb/406f00. The repeating406eb0 initialization loop was excluded. This numerical result does not satisfy the visual gate.
Transport-output incident: total serialized API response bytes exceeded the stated1MiB cumulative output cap while PNG base64 was being collected. Exact response counts are in incidents.json. The first collector was interrupted after the before frame, discarding a partial after transfer; the earliest after was subsequently collected. Image transport remains within the selected-capture disk allocation, and the guest itself emitted only13705 text bytes, but cumulative API-output compliance is not claimed. No platform denial was bypassed. This evidence is a truthful failure closeout, not a qualified acceptance pass.
The exact291-file15760340-byte mixed immutable manifest was transferred in435 finite batches and every file rehashed remotely before guest execution. Manifest SHA256 4141f5ff9e95ad35f8891394d79706a9a9a4792fe8dffce8f0f59bc4633ed5fd; its rows identify donor/revision/path or immutable local source. Runner revision5691793a58b4670fd2a621114d7926100a1e47de, SHA256 3c59fd034391e069f24a6047cf96cd8dac84a791d7d7591d55e5f7cb6e161a5e. Historical Wasm SHA256 8fac39936b6df2418ad86cab118cef19a65a727f649fbc14c412b37818904686, not current-main. Original EXE SHA256 14d6e430c26c44c94ef5c176eca2f66edd82dd66fd155d29a5596e3d6e170fc1. Prior passed numerical/codec/layout/source groups were referenced, not repeated. The exact runner canonical getArg/getArgs and DLL parser plus production expandIncludePatterns enumerated all83 graphics and7DLLs; there are no comma-bearing intended filenames. No source surrogate established production behavior.