Traverse v0.11.0: one real runtime.wasm orchestrator

[enricopiovesan]

What shipped

Traverse v0.11.0 is out. Minor lockstep crate + npm cut. 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). traverse-registry stays at =0.21.0. npm traverse-embedder-web@0.11.0 is published and aligned with this cut.

Highlights worth caring about

1. Real nested-wasmi runtime.wasm — traverse-runtime-wasm hosts the nested-wasmi executor; shared engine-agnostic emit_event / placement validation lives in traverse-contracts so Wasmtime (native) and nested wasmi share one core. traverse-native-bridge builds the real artifact on the unchanged runtime-wasm-bridge/1.0.0 ABI.
2. Production host driver + three-native-host conformance — RuntimeWasmHost loads/dispatches/drains lifecycle and domain 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 BundleEmbedder and composedWorkflow load digest-verified runtime/runtime.wasm from the app bundle and drive the same bridge ABI as native. Interim TypeScript wasi.ts / emitEventHost.ts and per-capability Host ABI import gating are gone.

Also in the cut: lockstep crate/npm versions on every cut (Decision 85), and 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 — versions are lockstep.
• If you consume traverse-registry directly, pin =0.21.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). This is Traverse platform work on the existing Spec 137 model.execute host-connector port — not shipped in the v0.11.0 cut:

• Exact signed model references — app manifests pin exact_model_dependencies; packages ship a sidecar manifest with digest, license, ABI, schemas, and resource limits. Never a naked URL.
• Provider-neutral command envelopes — versioned Spec 137 model.execute 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 cache — Spec 526 verified cache for model packages; offline execute when provisioned and the manifest allows it; miss → stable model_unavailable.
• First conformance: wasm-cpu — deny-by-default FS/network for the model guest; later acceleration adapters must preserve the public envelopes.
• Same envelopes for browser and native — placement is metadata; browser cross-target conformance follows the native path.
• Fail-closed — verified digest/signature, unknown fields rejected, redacted traces (no tensors/secrets/credentials).

Spec 045 (candidate / LLM resolution) remains a separate track.

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.html
• crates.io: https://crates.io/crates/traverse-runtime/0.11.0
• npm: https://www.npmjs.com/package/traverse-embedder-web/v/0.11.0
• /discover (browser flow): https://traverse-framework.com/discover.html

If this is useful, a star on traverse-framework/traverse helps other people find it. No spam, no invite spam — just the release.

[enricopiovesan]

Progress note (same day as the cut)

Spec 138 exact-ref governed model.execute landed on main after the v0.11.0 publish:

• Merged: feat(runtime): Spec 138 exact-ref model execution (#1435–#1437) #1438 (closes the Spec 138 / ADR-0074 / native+browser wasm-cpu conformance tickets)
• Release cut in flight: chore: cut Traverse v0.12.0 (Spec 138 exact-ref model.execute) #1445 + bump PR chore: bump version to v0.12.0 #1446 for v0.12.0 so the published crate/npm line carries Spec 138

Still honest about scope: this is portable exact-ref model package execution on the existing Spec 137 model.execute host-connector surface — not Spec 045 candidate/LLM resolution, and not a claim that every host already ships a certified public model-runtime package. Pin versions after the v0.12.0 tags land.