Consume published native embedder packages (drop path/vendor deps)

[enricopiovesan]

Summary

After Traverse publishes Maven Central dev.traverse:traverse-embedder, nuget.org TraverseEmbedder, and a v*-aligned TraverseSwiftHost.xcframework, switch App-Refs off TRAVERSE_REPO / vendor/traverse-embedder-dotnet path deps.

Governing spec

Traverse Spec 136 (ticket traverse-framework/traverse#1366) and Decision 83. Spec 068 FR-010 already has the no-sidecar shells; this ticket is the published-coordinate cutover.

Why

Android settings.gradle.kts includes :traverse-embedder from $TRAVERSE_REPO. WinUI uses ProjectReference to vendor/traverse-embedder-dotnet. That is not a downstream-consumable Shipped path.

Depends on

• Apple: rebuild TraverseSwiftHost XCFramework on wasmi 2.0.0 traverse#1370 (XCFramework on the shared v* tag)
• Android: publish traverse-embedder to Maven Central traverse#1371 (Maven Central)
• Windows: publish TraverseEmbedder to nuget.org traverse#1372 (nuget.org)

Blocked by

Those three must be published on the same Traverse v* tag before this can close.

Definition of done

• Android Compose shells depend on dev.traverse:traverse-embedder from mavenCentral() only
• WinUI shells PackageReference nuget.org TraverseEmbedder (no vendor project)
• SwiftPM / Xcode pins the release XCFramework / package version that matches that v*
• README / sync scripts no longer require a Traverse checkout to build the native shells (bundle sync may still need published runtime artifacts)
• CI green without TRAVERSE_REPO for those package resolves

Validation

• Clean clone, no sibling Traverse repo: Android Gradle resolve + WinUI restore + Swift package resolve succeed against public registries
• Embedded submit still runs without traverse-cli serve