Embed WASM runtime: Linux GTK + CLI Rust (#117)

[enricopiovesan]

Summary

• Migrate traverse-starter and doc-approval linux-gtk + cli-rust shells from the HTTP sidecar to the public traverse-embedder SDK (BundleEmbedder / EmbedderTestDouble)
• Zone 1 shows Embedded runtime mode + Ready/Unavailable; prefs drop sidecar URL in favor of workspace + optional manifest path
• Unit/integration tests use host SDK test doubles (no fake business logic)
• manifests/traverse-starter/app.manifest.json: state_machine invoke uses declared capability traverse-starter.process so bundle registration succeeds (registry does not accept workflow ids in invoke); Phase 3 shells still submit traverse-starter.pipeline via embedder
• Doc-approval production bundle init remains Unavailable until #112

Governing Spec

• Traverse 068-public-platform-embedder-packages
• Traverse 057-embeddable-runtime-host (embedder-api/1.0.0)
• Traverse 058-workflow-pipeline-execution
• App-References docs/embedded-runtime-plan.md / docs/design-language.md

Project Item

• Issue: Embed WASM runtime: Linux GTK + CLI Rust clients (traverse-starter + doc-approval) #117
• Project 2 item: PVTI_lADOEbiBt84BbzAzzgx7YnM

Definition of Done

• GTK + CLI launch without traverse-cli serve on the production path
• HTTP sidecar removed from GTK/CLI production path
• Zone 1 shows Embedded runtime status
• Tests use EmbedderTestDouble, not fake business field computation
• cargo test for core + CLI packages passes
• Board docs updated (AGENTS.md, README, design-language, embedded-runtime-plan)

Validation

• cd apps/traverse-starter && cargo test -p traverse-core-rs -p traverse-starter-cli
• cd apps/doc-approval && cargo test -p doc-approval-core-rs -p doc-approval-cli
• bash scripts/ci/repository_checks.sh
• TRAVERSE_STARTER_MANIFEST=…/manifests/traverse-starter/app.manifest.json cargo run -p traverse-starter-cli -- health --json → Embedded / Ready
• Live run against current Traverse example WASM stubs still fails (registered artifact execution failed) — stubs are 36-byte _start fixtures; executable agents are a Traverse follow-up. Host boundary is covered by test doubles.

Architecture boundary

• UI/shells only call public traverse-embedder APIs
• No private Traverse internals imported
• No business fields computed in UI

Made with Cursor