> Verdict: build now.
The browser is where the engine already works, and the plugin design writes itself: one shared engine pair per Livecode version, cached by the browser across every widget; a small `standalone.zip` per widget, selected through the `Module.livecodeStandalone` override; the trimmed shell from Wasm Snips; lazy boot on click and htv style teardown, because 6.4 MB of wasm plus runtime memory per instance demands a one live widget policy.
The `WebpageInteractionStack` demos in the wasm assets are the postMessage bridge prior art. The forty stack `lcw` mono repo becomes a widget quarry, authored in the IDE. `wiki-plugin-livecode` is the next concrete build.