Ship traverse-starter.pipeline multi-capability showcase

[enricopiovesan]

Summary

• Retarget manifests/traverse-starter to traverse-starter.pipeline with validate/process/summarize components and state_machine invoke
• Parse and render namespaced final output (validate / process / summarize) across web, Swift, Rust, Android, and Windows clients
• Point Android/Windows execute capability at traverse-starter.pipeline; update Phase 1/2 smoke nested field assertions

Governing Spec

• Traverse pipeline workflow (traverse-starter.pipeline) and capability contracts on Traverse main
• 033-http-json-api / 059-http-command-dispatch

Project Item

• Closes Multi-capability showcase: traverse-starter.pipeline workflow (validate → process → summarize) #110
• Project 2 item for Multi-capability showcase: traverse-starter.pipeline workflow (validate → process → summarize) #110

Definition of Done

• App manifest references pipeline workflow + three component manifests
• Platform UIs invoke workflow via single submit { note } (commands) or pipeline capability (execute clients)
• Combined final output + trace rendered (namespaced fields)
• No business field computation in UI

Validation

• cd apps/traverse-starter/web-react && npm test (19 tests)
• cd apps/traverse-starter/TraverseCore && swift test
• cd apps/traverse-starter && cargo test -p traverse-core-rs -p traverse-starter-cli
• bash scripts/ci/repository_checks.sh
• Sidecar register + pipeline execute (requires linked Traverse _traverse checkout with pipeline artifacts)

Architecture boundary

• UI shells render runtime fields only
• Workflow JSON remains in Traverse; App-References only references it

Checklist

• Issue linked and Project 2 item updated
• Updated AGENTS.md / README.md
• No business logic added to UI layer
• CI gates pass locally where applicable

Made with Cursor