Release history

Browser adapter, MCP server, React demo

The largest release to date. Introduces the live browser adapter, the MCP stdio server for AI agent integration, and the React demo app. All backed by the expedition planning example domain.

• Live browser adapter on port 4174. UI submits governed requests, runtime executes WASM capabilities locally.
• React demo app on port 4173 — connects to browser adapter, shows real-time state transitions and trace output
• MCP stdio server (traverse-mcp). AI agents discover and execute governed capabilities via Model Context Protocol.
• Expedition planning domain with 6 capabilities, 5 events, and 1 workflow. Fully governed and runnable.
• Trace generation and subscription. Every execution produces a structured, queryable trace artifact.
• State machine: ready → streaming → completed with ordered runtime timeline
• Release-facing documentation: quickstart, authoring guides, troubleshooting

• foundation-v0-1: Core runtime, CLI, MCP surface
• capability-contracts: Contract definitions and validation
• event-contracts: Event contract definitions
• spec-alignment-gate: CI merge gate
• capability-registry: Registry behavior
• runtime-request-execution: Execution model
• workflow-registry-traversal: Workflow composition
• expedition-example-domain: Example domain definition
• expedition-example-artifacts: Example contracts and workflows

• 100% test coverage, CI-gated with no exceptions
• #![forbid(unsafe_code)] enforced across all crates
• No unwrap, panic, or TODO in production code
• SBOM generation (CycloneDX format)
• ADR process in place. All architectural decisions documented.

Release artifacts and app registration

Introduced stable release artifacts and the app registration and validation flow through the CLI. First version with a consumer-facing bundle integration path.

• Stable release artifacts, versioned and reproducible
• App registration via CLI using traverse-cli bundle inspect
• App validation through the registry bundle manifest
• Consumer-facing documentation and bundle integration path
• Release-facing entry path for downstream consumers

Spec governance, runtime foundation, CLI

Established the spec-driven development process, the core runtime crates, and the initial CLI surface. The foundation all subsequent releases are built on.

• traverse-runtime: core execution engine scaffolding
• traverse-contracts: contract parsing and validation
• traverse-registry: capability and event registry
• traverse-cli: initial CLI with register, list, validate, and run commands
• Spec governance process in place. Spec-first, ADR-backed, CI-gated.
• Rust workspace structure with #![forbid(unsafe_code)]
• First approved governing spec: foundation-v0-1