traverse-embedder

Public Traverse platform embedder SDK for Rust hosts — the Linux GTK and CLI delivery of spec 068-public-platform-embedder-packages, implementing every embedder-api/1.0.0 operation against an application-owned bundle. Production execution requires no traverse-cli serve sidecar and no .traverse/server.json discovery.

Supported platforms

Linux and any host with a Rust toolchain (the crate is pure Rust over the natively linked Traverse runtime; macOS and Windows work for development). The platform value in EmbedderConfig gates compatible-mode capabilities against their manifest platforms[] allowlist.

Operations

use serde_json::json;
use traverse_embedder::{BundleEmbedder, EmbedderConfig, TraverseEmbedderApi};

let mut embedder = BundleEmbedder::init(EmbedderConfig::new("app/app.manifest.json"))
    .expect("bundle should initialize");
embedder.subscribe(Box::new(|event| println!("{event}")));
embedder.submit("my-app.process", &json!({ "note": "hello" }));
embedder.shutdown();

Bundle input shape

init consumes the app.manifest.json bundle defined by spec 044-application-bundle-manifest: component manifests, capability contracts, digest-verified WASM artifacts, and workflow definitions, all application-owned and shipped with the host binary.

Runtime-WASM compatibility

The Traverse runtime is linked natively into this crate at the same workspace version; the Rust package ships no separate runtime-WASM artifact. Bundle WASM components must target the Traverse host ABI supported by the linked runtime. Incompatible bundles (unsupported schema_version, digest mismatch, invalid manifests) are rejected deterministically at init with a stable error code — never by falling back to a sidecar (spec 068 NFR-001).

Shutdown and cancellation

shutdown force-terminates every running compatible instance (emitting state_changed events with state killed), then rejects all further operations with runtime_stopped. It is idempotent.

Error mapping

Boundary failures use stable EmbedderErrorCode values (bundle_load_failed, unsupported_bundle_schema, runtime_stopped, target_not_found, compatible_lifecycle_required, platform_not_supported, instance_not_found, instance_not_running, …). Runtime execution failures surface inside error events with the runtime's stable snake_case codes (execution_failed, capability_not_found, …). Secrets never appear in errors, events, or evidence (spec 068 NFR-004).

Test double

EmbedderTestDouble implements the same TraverseEmbedderApi boundary with scripted results, identical event envelopes, deterministic identifiers, and the same compatible lifecycle — for host tests without WASM or file I/O (spec 068 FR-006).

Upgrade policy

• Embedder API 1.0.0; a new IDL version requires a new conformance suite revision and a release stating the new version in its evidence.
• Supported bundle schema versions: 1.0.0.
• Semantic versioning; the workspace currently versions in lockstep.

Release evidence

release_evidence() returns JSON recording the package name/version, the linked runtime version and linkage, embedder API + conformance versions, supported bundle schemas, and the digest of every bundled WASM component (spec 068 FR-008, NFR-002).

Conformance

tests/conformance.rs executes the shared spec 057 corpus: init-shutdown, wasm-capability-submit, compatible-lifecycle, platform-guard, and determinism. Certification metadata:

{ "traverse_embedder_api": "1.0.0", "conformance_passed": true }