feat(traverse-starter): Spec 001/002 event-UI parity across shells

[enricopiovesan]

Summary

• Apply Spec 001 presentation-state and Spec 002 capability-progress mapping across traverse-starter shells (web via event-ui-conformance, Rust core for CLI/GTK, Swift TraverseCore, Android, Windows).
• Surface presentation / active-capability fields on host run results and light UI chrome without inventing business fields in the UI layer.
• Keep fixture loaders Node-only (removed from package public exports) so web typecheck stays clean.

Project Item

ticket-id: event-ui-parity-traverse-starter

Definition of Done

• Language-equivalent Spec 001/002 mappers land for web, Rust, Swift, Kotlin, and C#
• Host run results expose presentation state / progress / active capability on each primary shell
• Unit tests cover mapper happy / blocked / idle (and web host asserts presentation on scripted runs)
• UI remains a rendering layer — no business-field computation added

Validation

• npm run test -w packages/event-ui-conformance
• npm run test -w apps/traverse-starter/web-react
• npm run typecheck -w apps/traverse-starter/web-react
• cargo test -p traverse-core-rs (from apps/traverse-starter)

Architecture boundary

UI shells only map and display public embedder event streams; pipeline business fields continue to come from the Traverse runtime.

Made with Cursor