v0.0.2 to v0.0.4: the boundary tax

The host boundary stops walking the whole heap per re-entry; an O(heap) walk is removed from the interpreter-only WASM build; JSON.stringify ×4000 drops from 919 ms to 8.5 ms; wasm-opt is dropped after measurement.

The day after the first release, the first embedders' workloads exposed the cost of crossing into the VM. v0.0.2 (a70cef47) stopped the host boundary from walking the whole heap on every re-entry and raised parser sandbox limits that had rejected real code. v0.0.3 (d71168a9) removed another O(heap) walk, took JSON.stringify ×4000 from 919 ms to 8.5 ms, shrank the bundle from 6,018,862 to 5,668,533 raw bytes, dropped wasm-opt because -Oz measured smaller raw but larger on the wire and slower, and pre-warmed the playground Worker after finding that a 68 ms delay was V8 compiling, not the engine. v0.0.4 (769c68ce) added getGlobalsFingerprint, a content digest so a mutation through a reference cannot be missed, cutting per-tick host sync from 9.6 ms to 2.1 ms.