Multi-capability showcase: traverse-starter.pipeline workflow (validate → process → summarize)

[enricopiovesan]

Summary

Define and ship a multi-capability workflow for traverse-starter: traverse-starter.pipeline chaining three WASM agents so all platform clients can showcase orchestration.

Why

Single-capability execute hides workflow composition. Phase 3 requires at least one app demonstrating multiple capabilities in one workflow.

Depends on

• Traverse WASM agents: validate, process (exists), summarize
• Updated manifests/traverse-starter/ with workflow + component manifests

Blocked by

Sidecar dev path (can start when #554 lands):

• Traverse #554 — traverse-starter.validate and traverse-starter.summarize WASM agents

In-app embedded E2E (Phase 3 — additionally blocked on):

• Traverse #553 — embeddable in-app runtime host SDK

traverse-starter.process already exists; #553 does not block sidecar-only pipeline authoring and manifest work once #554 is done.

Definition of Done

• Workflow JSON + three component manifests in Traverse examples
• App manifest in manifests/traverse-starter/ references pipeline workflow
• All platform UIs invoke workflow (single submit) and render combined final output + trace
• No business field computation in UI

Validation

• Sidecar dev path: register manifest → execute pipeline → all output fields present
• Unit tests for output parsing cover new fields (summary, wordCount, validation issues)

[enricopiovesan]

Board hygiene: clarified #554 blocks sidecar pipeline work; #553 blocks in-app embedded E2E only. Project 2 note updated.