Original Penguin Command integrated-clock firing checkpoint, 2026-10-24
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.
Firing causality remains unknown. Stopped after the control; no firing treatment was launched. The first control capture at batch35000 still shows the authentic menu. The intended adjacent firing baseline at35999 is also the same menu (identical encoded size; its remote file remains retained). The required first-frame gameplay/cannon checkpoint therefore failed before the planned A-down36000 / A-up36200 treatment. A later full-client frame shows Starting Wave #1 and all cannon/ammunition groups, but does not retroactively make the planned firing window a matched ordinary-play baseline. No third run, repair, alternative guest state, or treatment was attempted.
Evidence is in the adjacent directory (historical artifact: penguin-command-integrated-clock-firing-20261024/). Session01a16c3a-490f-7473-bb9d-c9a32cbaa418 owns this single task on
task/penguin-integrated-clock-firing-oct24; private explicit sparse checkout
repo. Root tracked files/index/refs
and all donors were read-only; root messageboard updates were append-only.
Execution compatibility passed before the control
This is new runner5691793a58b4670fd2a621114d7926100a1e47de with historical module/sourceb41a7c5f4b752d1f0bdab1141a11d4fed4dc6f9a, not current-main Wasm qualification. No compilation was requested or performed. The source-only independent acceptance was reused; only the execution diagnostic prerequisite was rerun.
- Historical normal module:1879746 bytes,
SHA256
8fac39936b6df2418ad86cab118cef19a65a727f649fbc14c412b37818904686. - New runner:687068 bytes,
SHA256
3c59fd034391e069f24a6047cf96cd8dac84a791d7d7591d55e5f7cb6e161a5e. - Original EXE:107008 bytes,
SHA256
14d6e430c26c44c94ef5c176eca2f66edd82dd66fd155d29a5596e3d6e170fc1. - Complete accepted import/type/memory ABI reused by exact immutable module
hash, with native import-name/kind equality for all291 entries and
DIRECT_WINDOW-inclusive fingerprint
9a3bc9149d58209cmatching the new mirror. The full original accepted contract was used remotely and is retained by the accepted scheduled-input task; this task's preflight receipts record it. instantiate-preload.cjswraps the real runner's WebAssembly.instantiate, actually instantiates its production host table with fixed shared512MiB, and exits immediately after success, before any guest export is called. This is a preguest linkage test, not an extra guest run or a stub host.- Production rasterCanvas/renderer and pngjs7.0.0 fixture passed; roundtrip pixels were[1,2,3,255]. All subset fonts were readable. The actual production input clock-domain regression passed, including its rejecting mutations.
- All original287 files/15719953 bytes passed the local complete hash gate, including7DLLs/83graphics/23pngjs files and the complete font set. The exact-main host helper closure yields291 files/15760340 bytes. All291 destination hashes passed after the one streaming transfer. Its432 serialized payload requests were each<=36000 bytes. No local media copy, archive, package, download, source build, fabricated DLL or asset edit.
Control and actual consumed/dispatched timing
All actions/captures were prequeued through supported --input=. Both planned
argv/schedules are retained, but treatment-args.json was never executed. The original README documents A/S/D or the three mouse buttons for cannons;
the planned variation was balanced A-down/up with the same normal-game entry,
aim(260,220), tick policy, captures and output endpoint as control.
| Observation | Actual evidence |
|---|---|
| Mouse move scheduled33000 | Dequeue/dispatch33007; focused hwnd0x10001 |
| Menu down scheduled34000 | WM_LBUTTONDOWN dequeue/dispatch34004; guestMs6800800; lastGuestTick6800803 at dispatch |
| Release scheduled34500 | WM_LBUTTONUP dequeue/dispatch37629; guestMs7525800; lastGuestTick7525801 at dispatch |
| Aim scheduled34800 | WM_MOUSEMOVE dequeue/dispatch37629; guestMs7525800; lastGuestTick7525803 at dispatch |
| First frame35000 | Full original menu, no gameplay cannon baseline; guestMs7000000, lastGuestTick6900000 |
| Planned before35999 | Menu, preceding any cannon observation; guestMs7199800, lastGuestTick6900000 |
| Frame38000 | Score0, Starting Wave#1, Defend Cities, six cities, all three bottom cannon/ammunition groups; cross at(260,220) |
| Frame40000 | Score0, ordinary play, all three cannons and ammunition visible; green descending lines without a firing key |
| Frame42000 | Score80, Wave Scoring; no firing variation was supplied, so this score cannot establish firing causality |
These are accepted production --trace-input-dispatch observations, not
guessed delivery from scheduled batches. Renderer-origin enqueue IDs and
DispatchMessage correlation remain explicitly unavailable, as designed. The diagnostic records the actual last guest tick return separately from
published guest time. The menu down dispatched earlier than release/aim;
37629 must not be described as the time of all menu input.
The host canvas is840x660 using supported --screen=840x660. The complete
800x600 client is inside the window at desktop(20,20), below its title bar. The lower cannon/ammunition groups and right border are visible in the later
control frame. Unlike the old640x480 capture, no right/bottom clipping is
observed. Nevertheless, the first required gameplay checkpoint was a menu,
so the assignment's stop-before-firing rule was applied. No projectile,
blast, ammunition response, score-based firing success, audio, FPS or full
game claim is made.
Recovery, resources and handoff
Executed recipes and source identities are retained verbatim. They use their original taskroot/remote paths; do not replay them over existing output paths. Immutable source/media/module/CRT/pngjs donors are named in manifest.json. Setup resolves explicit exact-main file blobs and a focused require closure; private alternates are flattened without donor mutation. Historical manifest identity is independently checked before replacing the runner closure.
Concrete resume condition for the coordinator: a new bounded assignment must choose its first control gameplay capture after actual ordinary menu-release/ aim consumption and confirm a matched cannon/ammo baseline before any firing variation. This task does not schedule that replacement or consume another run.