Define app ownership boundary and relocate runtime fixtures from apps/

[enricopiovesan]

Outcome

Make traverse-framework/reference-apps the home for checked-in application UI and client-demo source. Keep only runtime-owned conformance fixtures, manifests, and agents in the Traverse repository, under an examples/-based location rather than apps/.

Why

apps/ currently mixes platform reference clients with runtime fixtures. That duplicates the stated purpose of reference-apps, obscures ownership, and makes runtime releases carry application-source maintenance.

Scope

• Record the ownership rule in the decision log: checked-in application UI and reference clients belong in reference-apps; runtime conformance fixtures belong in Traverse examples/.
• Publish a path-by-path migration inventory for every current apps/ entry, with owner and destination.
• Relocate runtime-only fixture/manifests (including demo fixtures and application manifests) to an examples/ location that reflects their conformance role.
• Update Traverse docs, scripts, CI, and tests to the new fixture paths.

Out of scope

• Migrating UI/client source itself (tracked by dependent Reference Apps tickets).
• Changing the public SDK contracts.

Definition of done

• Decision log records the app-source versus runtime-fixture ownership rule and links the migration inventory.
• Every current apps/ path is classified as Reference Apps, Traverse fixture, or retired, with an explicit destination.
• Runtime-owned artifacts are under examples/; no new runtime fixture is introduced under apps/.
• All affected docs, CI, scripts, and tests use the relocated paths.
• A focused validation proves the moved fixtures still run against the same public runtime contract.

Dependencies

None. This establishes the boundary required before dependent migrations can start.

[enricopiovesan]

Implementation complete in auto-merge queued PR #707. Local evidence passed: app ownership boundary smoke, full repository checks, spec alignment, and git diff check. After two bounded polls, required repository/stress jobs remain pending with no failures; moving Project 1 to Blocked on external CI capacity until the queued PR merges.