Traverse v0.10.1 + /discover: governed composition you can click

[enricopiovesan]

What shipped

Traverse v0.10.1 is a compatibility-preserving patch on the v0.10 line — runtime, browser embedder, and CLI authoring path. Highlights:

• Native WasmExecutor treats WASI proc_exit(0) as successful completion (nonzero still rejected).
• Web embedder supplies deterministic denied shims for approved connector imports so ABI-valid modules load without ambient connector authority.
• traverse-cli app new writes app.manifest.json, matching the documented bundle convention.

No migration for existing apps. crates.io packages are at 0.10.1.

Try the public browser flow

/discover is the clickable sibling of governed composition for the browser embedder:

1. Pick a structured goal
2. Browser pulls the live public registry and builds a digest-verified snapshot
3. A deterministic structural planner (Spec 1277) proposes a workflow from schema shape — no name-matching, no natural language, no model
4. You review unconfirmed field mappings
5. The local governed runtime executes in your tab and returns a redacted per-node trace

No backend. No simulation. Failures stay failures.

Honest bounds

/discover is not an AI agent, not “the browser is the authority,” and not a claim that any free-text goal works. It proves structural planning + review gate + fail-closed browser-local execution for a small authorized risk class.

Full writeup: What /discover proves — and what it doesn't

Links

• Release: https://github.com/traverse-framework/traverse/releases/tag/v0.10.1
• /discover: https://traverse-framework.com/discover.html
• Blog: https://traverse-framework.com/blog/what-discover-proves.html
• Spec 1277: https://github.com/traverse-framework/traverse/blob/main/specs/1277-browser-local-workflow-composition/spec.md