Adopt Traverse starter/reference material from runtime repo

[enricopiovesan]

Outcome

Adopt the checked-in youaskm3-starter-kit and other application-starter material currently under Traverse apps/ as a Reference Apps-owned starter/reference artifact.

Scope

• Establish the canonical Reference Apps location and ownership for the starter material.
• Separate reusable/reference material from runtime-only manifests and fixture agents.
• Preserve a runnable starter validation using only documented public Traverse integration points.
• Update guides and links so downstream developers do not start from a runtime-repository apps/ path.

Definition of done

• Starter/reference source has a canonical home in reference-apps with an owner and supported validation command.
• Runtime-only fixture manifests and agents remain in Traverse under its post-boundary examples/ location.
• The starter runs against documented public Traverse APIs/contracts with no private path dependency.
• Documentation directs users to the Reference Apps artifact.
• The corresponding Traverse apps/ starter source can be removed without losing the supported onboarding path.

Dependency

Blocked until the Traverse ownership/fixture-boundary ticket publishes the path inventory and fixture destinations.

[enricopiovesan]

Project state: Blocked on traverse-framework/traverse#703. That ticket determines which starter contents are reference material versus runtime-owned fixtures and their destinations.

[enricopiovesan]

Consolidated into #151 to keep one migration ticket for all application and starter/reference source. #151 now contains this ticket’s scope and definition of done.