Automerge WASM and Browser Builds

Current status

There is no active HyperToken WASM backend. The former Rust-to-WASM core, WasmBridge, WasmChronicleAdapter, and WasmManager were removed. All actions route through engine.dispatch() to the TypeScript ActionRegistry, which mutates the TypeScript Chronicle backed by Automerge.

What “WASM” means in the browser build

The browser bundler aliases @automerge/automerge to Automerge's fullfat_base64 entry point. That dependency packages Automerge's own WASM implementation into the JavaScript bundle. It is an Automerge runtime packaging detail, not an alternate HyperToken state or action backend.

Build a browser entry with the shared script:

node --loader ./test/ts-esm-loader.js core/browser/build.js \
  --entry examples/watershed/web/watershed-web.js \
  --out examples/watershed/web/watershed.bundle.js

The historical Rust integration is preserved outside the current runtime in the repository's WASM_INTEGRATION.md history notes.