Independent midiStreamStop acceptance (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.

Accepted candidate 2def2064ac4461974e665ea7c47d10cc2073509c within compiled focused-handler scope. No production implementation changes.

Run node --max-old-space-size=192 test/test-midi-stream-stop-independent.js. The new oracle independently extracts the production Open, Out, Stop, notification, service and Restart functions and all stream globals, compiles them through the candidate's vendored WATX compiler, and executes the resulting Wasm. It prints source, extracted-form and module hashes. The fixture uses eight memory pages, a nonidentity guest mapping, and explicit host/interpreter endpoint doubles.

Passing adversarial cases:

The unchanged candidate focused test passed once as the first behavioral group. An exact parent-table comparison verified that all 4534 old API rows remain unchanged and the sole new row is ID 4534, midiStreamStop, stdcall with one arg. Both exact candidate generators passed --check against the production tables. Git comparison also verified that the materialized production/compiler inputs remain unchanged from the candidate. No full VM build was needed.

Two fixture failures are retained: unsupported inline memory export syntax, then a nonreturning-run double incorrectly advancing ESP as if it had returned. Only the fixture was corrected; the production implementation and behavioral oracle requirements were unchanged. The final test passed after those repairs.

Limitations: no actual x86 callback body, full guest/gameplay, OS notification delivery, host synth implementation or full VM dispatch execution was tested. The run endpoint supplies RET 20 or a bounded nonreturning simulation. Generator freshness establishes API wiring structurally. No Boat/runtime was allocated, no main integration was performed, and there was no public deployment.