Maelstrom 3.0.6 original Win32: tree-mounted runtime, 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.

The original menu renders and ordinary P changes it to a sparse starfield. Visible gameplay, movement and firing remain unproven. The single bounded run completed 42000 batches in 3.685 guest-loop wall seconds, naturally exiting the harness with code0 after 3.861 seconds total. No trap, missing-file error, unimplemented failure or output/time guard occurred. Both post-P captures contain stars on black and a teal bottom strip, with no visible ship, HUD or shot. This is a bounded gameplay no-hit, with unknown cause, rather than a successful gameplay result. No second guest, production repair, build, registry change or main merge occurred.

All three actual captures were inspected: menu (historical artifact: maelstrom-tree-mounted-runtime-20261024/menu.png), after P (historical artifact: maelstrom-tree-mounted-runtime-20261024/play.png), after scheduled input (historical artifact: maelstrom-tree-mounted-runtime-20261024/input.png). The menu shows the title, high scores and “P Start playing Maelstrom.” The raw 6393-byte log (historical artifact: maelstrom-tree-mounted-runtime-20261024/output.log) establishes the ordinary P keydown reaching DispatchMessageA for HWND0x10001, followed by left/up/space keydowns. Those messages alone do not prove guest movement/fire effects. P keyup and left keyup also dispatched; up/space keyups were injected but their dispatch was not observed before the bound. Audio output was initialized at11025Hz/mono/8bit but audible sound was not assessed.

Inputs and mount correction

The previous per-file recipe failed because the authentic Docs/Ambrosia_Software,_Inc._FAQ.txt was split on commas. This run used the supported single --vfs-tree=vfs, containing only maelstrom/ with all48 original files and names. Guest executable and CWD were C:\maelstrom\Maelstrom.exe and C:\maelstrom; guest environment MAELSTROM_LIB=. and HOME=.. No networking/fullscreen options or forced game state were used. Score/config writes use the ordinary writable in-memory VFS; persistence was not tested.

The actual staged mapping (historical artifact: maelstrom-tree-mounted-runtime-20261024/tree-validation.json) rehashed all48 originals and validated the full actual argv using an extracted, unmodified canonical getArg/getArgs/hasFlag parser and canonical directory enumeration. It rejected the broken comma recipe, wrong guest root and missing file. Parser SHA256 is aa2d16119b2edc62abc08862fc7c3ea28a98bdc7fb4d28161937a1f705e4621e. The game tree totals2794170 bytes. The unchanged accepted906220-byte archive SHA256 is 6cc9ef78eda9a0c3591dbd6f67b8c534682ef3f30bda0acd3b0138a0a0c52db5.

Input Bytes SHA256
Maelstrom.exe 135168 0eca5703e512d33c5e5a0bc1a27f14bd3aa4ecddded6e09b4d4019c2f27a15e5
SDL.dll 225280 02433232425e68009843bd3ecec20ad67453a48487f7b5828c595b76e2f9d373
SDL_net.dll 24576 46ccbb7e5982e2c15421af7dd4fa29b26841d9731c31a86cf9554c90be53af95
System msvcrt.dll 278581 887eb5ce93edb7192ca3e9220f07f9ca0f94db02af5862ebcbdfcb852db99fd1
Historical full WASM 1879746 8fac39936b6df2418ad86cab118cef19a65a727f649fbc14c412b37818904686
Canonical test/run.js 685960 4d7b9587676db38fcf3314807acb2b2a42b5f09d2c98fcf3dccb8a6cde9e1809

The module is retained from source b41a7c5f4b752d1f0bdab1141a11d4fed4dc6f9a; this does not qualify current-main WASM. Compatible canonical harness source is revision d8cd8c54c8d63c107696f1e4ef7a1e229dcadc1e in /home/user/wine-assembly-shadow-man-span-static-canonical-oct23. The reused ABI inventory records291 imports, shared-memory min8192/max32768, matching layout stamp 9a3bc9149d58209c; actual instantiation succeeded. CRT, SDL and SDL_net relocated to0x522000,0x666000,0x7a2000, respectively, and initialized successfully. Both SDL preferred bases were0x10000000.

The 247-file manifest (historical artifact: maelstrom-tree-mounted-runtime-20261024/manifest.json) pins every source, codec, font, system DLL and game file:17027463 transferred bytes. Remote UID1000 rehashed every entry. pngjs7.0.0 came from the standing /home/user/wine-assembly/scratch/usage-watch/shadow-man-codec-recovery-oct22/node_modules/pngjs; package.json SHA256 85b17f2f852aece03e71edb4ed4d9fddf6a0a8f0b69ac75d7f00b6592d62d37c, full codec file hashes in manifest. No installation/download occurred. The complete harness dependency preamble, raster renderer and28 fonts loaded in the preguest probe.

Execution, controls and limitations

Command receipt (historical artifact: maelstrom-tree-mounted-runtime-20261024/command.json) records PID/PGID21471, UID1000, Nodev24.22.1, start2026-10-24T07:15:35.860Z, fresh MemAvailable7192854528. Explicit --no-build --wasm, software640x480 rendering, fixed512MiB shared arena, oldspace512MiB, CPU/wall90s, guest60s, max42000 batches, --quiet-api --quiet-blocks, output524288-byte cap. No native concurrent run. Host WINE_RUN_EXTRA_ARGS/WINE_REGION_MAP were removed.

The existing schedule was preserved: menu PNG30000; Pdown31000/up31200; post-P PNG34000; leftdown35000,up-arrowdown35200,spacedown35500,leftup36000,up-arrowup36200,spaceup36500; final PNG39000; limit42000. All planned injections preceded the limit. Actual input and window dispatch lines are retained in input-receipt.json (historical artifact: maelstrom-tree-mounted-runtime-20261024/input-receipt.json). Per-dispatch wall timestamps and batch numbers were not emitted and remain unknown. PNG timestamps record guest-ms6000000,6800000,7800000; these are synthetic harness clock values, not elapsed wall time or real-time gameplay qualification. Root cause of the absent ship/HUD is not established.

Three captures total45355 bytes (40715/2331/2309), each below131072; lossless decode/reencode preserved actual pixels. Preguest controls rejected invalid bytes and dimensions and verified real640x480 pixel roundtrips. The watchdog's TERM-resistant control required TERM then KILL after5s and reaped its group. The actual guest needed no signals; terminal receipt (historical artifact: maelstrom-tree-mounted-runtime-20261024/terminal.json) confirms no surviving group. The initial cleanup substring probe falsely included its own Python source; the corrected executable-name probe and rejecting control are retained without deleting the earlier receipt. Corrected probe confirms no task Node processes.

Recovery and handoff

The reviewed result.json (historical artifact: maelstrom-tree-mounted-runtime-20261024/result.json) records unknown for the complete gameplay objective, with menu and P transition proven separately. Identical ignored bundle: scratch/runs/20261024T071535Z-maelstrom-tree-01a16cc1/ in this private checkout; no shared-dashboard association or registry entry was added. Originals/module/runtime staging remain ignored retained inputs with recovery recipe, not Git-backed binaries.