Traverse v0.11.0: one real runtime.wasm orchestrator

[enricopiovesan]

What shipped

Traverse v0.11.0 is out — a minor lockstep crate + npm release. The throughline is one real runtime.wasm orchestrator: native hosts and the browser embedder all drive the same nested-wasmi capability executor inside an application-owned runtime.wasm, instead of a canned WAT fixture (native) or a hand-rolled TypeScript WASI/emit_event path (browser). Spec 1402-runtime-wasm-orchestrator-convergence is complete on main.

crates.io packages are at 0.11.0 (traverse-contracts, traverse-runtime, traverse-embedder, traverse-mcp, traverse-cli-rs, traverse-expedition-wasm). npm traverse-embedder-web@0.11.0 is published and aligned with this cut. traverse-registry remains a separate crate (currently 0.21.0 on crates.io).

Highlights worth caring about

1. Real nested-wasmi runtime.wasm — traverse-runtime-wasm hosts the nested-wasmi executor and audited C-ABI export boundary. Shared, engine-agnostic emit_event validation and placement constraints live in traverse-contracts, so Wasmtime (native) and nested wasmi share one core.
2. Production host driver + three-native-host conformance — RuntimeWasmHost loads, dispatches, and drains envelopes from runtime.wasm (EventBroker durability stays host-owned). Swift/wasmi, Kotlin/Chicory, and .NET/Wasmtime pass the bridge conformance corpus against the real artifact; digest published via runtime/native-runtime-registry.json.
3. Browser convergence — traverse-embedder-web loads digest-verified runtime/runtime.wasm from the app bundle and drives the same runtime-wasm-bridge/1.0.0 ABI as native. Interim TypeScript wasi.ts / emitEventHost.ts path is retired.
4. Release pipeline honesty — crate and npm versions stay lockstep on every cut (Decision 85), plus an honest Python CLI consume example.

Upgrade notes (short)

• Breaking (web embedder): app bundles must include runtime/runtime.wasm and runtime/runtime.wasm.sha256 (sha256:<64 hex>). Bundles that relied on the interim TypeScript executor fail at BundleEmbedder.init until those files are added.
• Rust crate APIs for existing local Wasmtime callers are unchanged.
• Native host adapters keep the same bridge export surface; they must resolve the new certified runtime.wasm digest via the native runtime artifact registry.
• Pin traverse-embedder-web@0.11.0 together with crates at 0.11.0.

Coming next (work in flight — not in v0.11.0)

Portable exact-ref governed model execution for WASM model packages is being implemented under Spec 138-governed-exact-model-execution and ADR-0074 (owner-approved; implementation tickets open). Public framing, grounded in those artifacts:

• Exact signed model references — app exact_model_dependencies pins; package sidecar manifest with digest, license, ABI, schemas, and resource limits. Never a naked URL.
• Provider-neutral Spec 137 model.execute command envelopes (versioned request/response) with opaque input_ref / output_ref; host stage_model_input / read_model_output for binary tensors. Guest model_invoke stays out of scope for Spec 138 v1.
• Registry resolve + content-addressed verified cache; offline execute when provisioned and allowed; miss → stable model_unavailable.
• First conformance: wasm-cpu; later acceleration adapters without changing the public contract.
• Same envelopes for browser and native embedders; placement as metadata.
• Fail-closed: verified digest/signature, deny-by-default FS/network for the model guest, redacted traces.

Spec 045 (candidate / LLM resolution) remains a separate track. This is platform work on main — not shipped in the v0.11.0 cut.

Links

• Release notes: https://github.com/traverse-framework/traverse/releases/tag/v0.11.0
• Changelog: https://github.com/traverse-framework/traverse/blob/main/CHANGELOG.md
• Site changelog: https://traverse-framework.com/changelog.html
• Blog: https://traverse-framework.com/blog/traverse-0-11-0-runtime-wasm-orchestrator.html
• crates.io: https://crates.io/crates/traverse-runtime/0.11.0
• /discover: https://traverse-framework.com/discover.html

If this is useful, a star on traverse-framework/traverse helps other people find it.

[enricopiovesan]

Closing as duplicate of the canonical Announcement: https://github.com/orgs/traverse-framework/discussions/1439 (same title; this one was a second post during the v0.11.0 cut). Please use #1439 for discussion.