Skip to content

Adopt Traverse platform reference clients from runtime repo #151

Description

@enricopiovesan

Outcome

Make this repository the canonical home for all checked-in application UI, platform client demos, and application-starter/reference source currently under the Traverse runtime repository's apps/ directory.

Scope

  • Adopt the React, browser-consumer, Android, and macOS client/demo sources currently maintained under Traverse apps/.
  • Adopt youaskm3-starter-kit and other application-starter/reference material as Reference Apps-owned artifacts.
  • Separate reusable/reference source from runtime-only manifests, fixture agents, and conformance inputs.
  • Preserve or replace each app's build, smoke, and public-contract validation.
  • Make every adopted artifact consume released/public Traverse surfaces only; no private runtime imports or repository-relative coupling.
  • Update user-facing documentation to point to the canonical Reference Apps paths.

Definition of done

  • React, browser, Android, and macOS reference clients have canonical homes in reference-apps.
  • Starter/reference source has a canonical home, owner, and supported validation command in reference-apps.
  • Runtime-only fixture manifests and agents remain in Traverse under the examples/ destinations established by the ownership-boundary ticket.
  • Each adopted application/starter has reproducible build or smoke validation in this repository.
  • All adopted artifacts use only intended public Traverse contracts or SDKs.
  • Documentation identifies this repository as the source of truth for applications and starter material.
  • The corresponding Traverse source directories can be removed without losing supported demo or onboarding coverage.

Dependency

Blocked until Traverse #703 publishes the ownership inventory and fixture destinations. Coordinate the platform slices with existing Reference Apps #113#116 and their SDK prerequisites; this ticket owns repository migration and source-of-truth acceptance, not SDK implementation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions