Traverse v0.16.1: catalog model.execute on published Browser and Node

[enricopiovesan]

Throughline

The catalog model.execute capability now runs on the published Browser and Node packages. v0.16.1 is an additive patch on v0.16.0: no breaking host ABI change, no exported symbol or bridge ABI version change. If you're already on v0.16.0, bump your pins to 0.16.1 and you're done. The loop is still discover → execute → trace: the model work stays in a WASM capability, the host only stages input, holds the trust root and answers the connector call.

What changed

• Catalog model.execute@1.0.0 on Browser and Node (Catalog model.execute@1.0.0 can't run on any published Browser/Node/Swift host: runtime.wasm and BundleEmbedder don't link traverse_host.connector_invoke, and there's no shipped traverse.model-runtime binding #1719, feat(#1719): catalog model.execute runs in Browser and Node #1770, Decision 122, Spec 1719). A guest can call a connector the host answers asynchronously. It suspends at connector_invoke, and the host's answer resumes it through the same Spec 104 checks.
• New web APIs in traverse-embedder-web: BundleEmbedder.activateMediatedConnector and exactModelMediatedConnector (the first-party traverse.model-runtime binding). Use submitAsync for these targets; sync submit fails them with async_submit_required.
• Output filter fix on every host (Spec 104 1.1.0 FR-008). The filter no longer refuses a signed model_evidence because it holds public URLs. Before, a real package failed with connector_unavailable. The filter still covers everything else.
• Shared cross-host vector fixtures/cross-host/model-execute-v1. ExactModelExecution gains output_schema_ref.
• Dependency bumps: wat 1.262.0, tonic-prost 0.14.7, zip 9.1.2, wasmparser 0.262.0, uuid 1.29.0. The Swift Package binary target at this tag points at swift-host-v0.16.0 (chore(swift): point Package.swift at the swift-host-v0.16.0 xcframework #1769), which fixes the stale pin in v0.16.0.

Minimal Browser and Native examples: docs/host-connector-command-dispatch.md

Run on the published packages

After the release, the published model.execute@1.0.0 guest ran unchanged over the signed traverse.digits-onnx@1.0.0 package on native (crates.io traverse-runtime 0.16.1), Node and Chromium (npm traverse-embedder-web@0.16.1). The success output, the 56-byte output frame, and six fail-closed cases (connector_unavailable, usage_undeclared, key_untrusted, pin_mismatch, digest_mismatch, package_revoked) matched on all three; native adds placement_evidence, which Spec 1719 allows. Evidence and scripts: #1782. A workflow (#1783) repeats it weekly on a fresh GitHub-hosted runner with only published packages installed.

Published

npm traverse-embedder-web@0.16.1 · Maven com.traverse-framework:traverse-embedder 0.16.1 · NuGet TraverseEmbedder 0.16.1 · crates.io traverse-runtime, traverse-embedder, traverse-contracts, traverse-mcp, traverse-cli-rs, traverse-expedition-wasm 0.16.1 (Rust 1.95) · Swift swift-host-v0.16.1 · traverse-mcp-v0.16.1 · onnx-runner-v0.16.1. runtime/runtime.wasm sha256 7a322a17e3fd58f8bd26e915dd81bad68732500dc981499bd280a6d2e6507d52.

Release notes · Changelog

Honesty footnotes

• Swift, Android and .NET activation APIs for this connector aren't shipped yet.
• runtime.wasm isn't in the npm package or a release (last runtime-wasm-v* is v0.11.0); take it from the v0.16.1 tag and check the digest. Tracked in runtime.wasm has no published release since v0.11.0, though BundleEmbedder apps require it #1784.
• On native, activate_exact_model_runtime doesn't let the caller read the output frame back (activate_exact_model_runtime can't read the output frame back on native #1785).
• The demo model is signed with the test-only key (Production model-signing key custody, distribution, rotation, and revocation (Spec 138) #1567). Registry spec 027 for model.execute is still a draft.
• Still pre-1.0; no host is Certified under Spec 529. Python is CLI-only (no Python SDK).