Traverse v0.10.2: verified Registry prep, Mode A/B MCP, host connectors

[enricopiovesan]

What shipped

Traverse v0.10.2 is out. Compatibility-preserving for existing local callers — crate APIs and the traverse-cli binary name are unchanged — and it lands the work that accumulated on main after the v0.10.1 compatibility fixes.

crates.io packages are at 0.10.2 (traverse-contracts, traverse-runtime, traverse-embedder, traverse-mcp, traverse-cli-rs, traverse-expedition-wasm). traverse-registry stays pinned at =0.20.0. npm traverse-embedder-web@0.10.2 is published and aligned with this cut.

Highlights worth caring about

1. Verified Registry application references — prepare an active signed Registry release into a host-owned cache under digest keys. app validate / register / activate consume that prepared evidence only. No fetch-at-activate, no version substitution, no credential requirement for the Callweave fixture path.
2. Mode A and Mode B MCP hosts — Mode A over host-owned verified public metadata; Mode B via traverse-mcp prepare-cache then traverse-mcp stdio --cache <dir> for discover/validate/execute/report from that cache alone.
3. Host connector command dispatch — public app-runtime port for a manifest-selected, explicitly activated host connector (audio.capture first; model.execute on the same envelopes).
4. Browser-local planning + composed execution — Rust embedder and traverse-embedder-web can plan deterministically and run a reviewed composed workflow offline. Plan-then-seal is the default; adaptive composition is opt-in.

Also in the cut: persisted capability hydration for serve, app availability status, ArtifactRouter WASI diagnosis, default WASM memory at 32 MiB, component-wit-v1 host bindings, CLI workflow plan / promote-finalize.

Upgrade notes (short)

• Registry-backed app validate / register / activate now require a prepared host-owned cache.
• Legacy serve registrations without a persisted state_machine need an explicit app register refresh (503 app_unavailable / app_registration_requires_refresh, not a silent 404).
• Pin traverse-registry =0.20.0 if you consume it directly.

Links

• Release notes: https://github.com/traverse-framework/traverse/releases/tag/v0.10.2
• 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-10-2-verified-registry-mcp.html
• crates.io: https://crates.io/crates/traverse-runtime/0.10.2
• /discover (browser flow, unchanged demo surface): 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.