Maelstrom complete transform contract — 2026-10-30
Historical source last updated, 2026-10-30. Runtime and implementation claims below describe that dated source; see current app notes and source for subsequent changes.
The actual production transform() at b115cacaf93ba01f526610126c72a185e6abf5c5
accepts the entire 13-fragment historical closure from
55f9724ef127100c3bb54aebca73e5cda5472c5f and the original binary bytes, with
{enabled:true,binaries:{net,crt,exe},crtLoadedBase:0x522000,uopNativeBoundaries:true}. No production code changed for this acceptance.
The first behavioral checkpoint was that complete production call, after verifying the helper, select hook, adapter, compiler and historical source hashes. The checked-in JSON manifest records all input pins and all 13 output hashes. Six fragments change: ALU RET, register CALL, UOP engine, UOP compiler, Win32 dispatch and Winsock. The other seven remain byte-identical. Inputs stay intact.
The standalone contract checks:
- Disabled calls return the identical input object, including hostile input and binary accessors that must remain unread (three cases).
- Every source fragment rejects a one-fragment mutation (13 cases), every binary rejects a one-byte mutation (three cases), and six invalid CRT bases reject.
- Full emitted source contains the select completion call, threaded CALL/RET hooks, both exact UOP instruction side exits, the switch hook before mode assignment, all scalar diagnostic exports, and all rejection reasons 1–36.
- The actual emitted
set_uopandmne_uop_switchforms execute in a tiny Wasm fixture. Both switch directions × active statuses 1/2/3 × four combinations of the other mode bits give 24 coherent rejections. Another 24 same-mode cases preserve state; six inactive/terminal cases emit no diagnostic. Three nonzero requests test normalization. Counted flush/refresh stubs verify that mode assignment and the original setter continuation still happen. - Production
decodeRejectionvalidates these emitted diagnostics, and productioncreateAdapterpersists all 27 rejection rows and seals each terminal owner. Wasm getters provide the diagnostic values. Start and unrelated select scalars are explicitly synthetic in this fixture. - A mutation removes only the production transform's boundary-PC diagnostic
assignment. The mutant still transforms the complete pinned closure. The
emitted-code oracle rejects it specifically because
rejectPCbecomes zero instead of0xf1234567; all other transformed bytes are checked unchanged.
Reproduction on the assigned host, from the owned repository:
python3 -B scratch/runs/<run-id>/ops.py reproduce /usr/bin/node --max-old-space-size=192 test/maelstrom-integrated-full-transform-contract.test.cjs scratch/runs/<run-id>/inputs scratch/runs/<run-id>/reproduced-manifest.json
The test pins every production dependency it uses. It reads original media only
from the standing paths recorded in the JSON manifest. Recovery also needs the
13 source files with the recorded hashes; inputs-manifest.json in the task
root identifies their standing or archived origins. No original media or full
generated output is copied into Git. The task's recovery recipe and patch live
outside the repository, alongside the completion receipt.
The first fixture attempt incorrectly wrapped the bare WATX forms in (module ...). The vendored compiler emitted an empty module, causing a missing setter
TypeError. Correcting that owned fixture required no production change and no
oracle relaxation. Final complete contract execution passed with empty stderr. The intermediate continuation and final strengthened mutant checks are retained
in task evidence; the old decoder-only acceptance was not rerun as a substitute.
This qualifies the offline complete transform and the emitted switch boundary under synthetic pre-state. The complete generated emulator was not compiled or instantiated. Select, CALL/RET, initialization ordering, guest execution, errno capture and end-to-end mode behavior remain unqualified beyond source inspection. There was no full build, browser, guest, gameplay, performance, causal-instruction or runtime claim. No Boat was allocated, and no public deployment or main integration occurred. The older build-inputs receipt does not qualify this helper.