Traverse v0.16.2: host-connector invokes in application manifests

[enricopiovesan]

Throughline

Application manifests can now invoke a declared host connector from traverse-cli. v0.16.2 is an additive patch on v0.16.1: no host ABI, guest ABI or bridge ABI version change. Existing capability-target manifests behave as before. If you're on 0.16.1, bump your pins to 0.16.2 and you're done.

What changed

• Host-connector manifest invokes in the CLI (Support host-connector invokes in application manifests and CLI activation #1772, fix(cli): support host connector manifest invokes #1788, Spec 1773). A state's invoke holds exactly one target: a capability ({"invoke":{"capability_id":"...","input_from":"..."}}) or a host connector ({"invoke":{"host_connector":"audio.permission.request"}}). The CLI registers the host-connector target as is. It never turns it into a capability reference.
• Bad manifests still fail closed. Empty, ambiguous (both targets) and malformed invokes are rejected before activation.
• Registry alignment. The release uses traverse-registry 0.31.0, which provides the typed exact-one ApplicationStateInvoke union.
• runtime.wasm rebuilt with runtime version 0.16.2.

Worked example and the fail-closed rules: Can a Traverse application manifest invoke a host connector?

Try it

cargo install traverse-cli-rs --version =0.16.2 --locked
traverse-cli app validate path/to/app.manifest.json

The shared runtime is a release asset now:

curl -LO https://github.com/traverse-framework/traverse/releases/download/runtime-wasm-v0.16.2/runtime.wasm
sha256sum runtime.wasm
# b313b5c5c11291d9e9669125a0a9a77aa42a911b15d431a73e86b17c874e298c

Published

npm traverse-embedder-web@0.16.2 · Maven com.traverse-framework:traverse-embedder 0.16.2 · NuGet TraverseEmbedder 0.16.2 · crates.io traverse-runtime, traverse-embedder, traverse-contracts, traverse-mcp, traverse-cli-rs, traverse-expedition-wasm 0.16.2 (Rust 1.95) · Swift swift-host-v0.16.2 · traverse-mcp-v0.16.2 · onnx-runner-v0.16.2 (same bytes as v0.16.1) · runtime-wasm-v0.16.2. runtime.wasm sha256 b313b5c5c11291d9e9669125a0a9a77aa42a911b15d431a73e86b17c874e298c.

Release notes · Changelog · Site changelog · Upgrade guide

Honesty footnotes

• traverse-cli app activate only registers its built-in reference connectors. traverse.audio-input isn't one yet (Register traverse.audio-input in the activation reference connector catalog #1791), so the audio example can't activate from the CLI today.
• The Swift Package at the v0.16.2 tag still pins swift-host-v0.16.1. main pins v0.16.2 (chore(swift): point Package.swift at the swift-host-v0.16.2 xcframework #1798), not released.
• Automatic runtime-wasm-v* publishing (feat(#1784): every product cut publishes runtime.wasm as a release #1797, closes runtime.wasm has no published release since v0.11.0, though BundleEmbedder apps require it #1784) is on main, not released. The v0.16.1 and v0.16.2 runtime releases were backfilled from their tags. npm still doesn't ship runtime.wasm.
• Known issue: on Swift, Kotlin and .NET, guests on this runtime.wasm read the {target_id, input} envelope instead of just the input (Native embedders appear to pass the whole target_id/input envelope to guests #1794). The fix (fix(#1794): guests on runtime.wasm receive only the submitted input #1800) is on main, not released. It breaks guests written to read the envelope.
• Still pre-1.0; no host is Certified under Spec 529. Python is CLI-only (no Python SDK).