Launch the new apps and transition the legacy app

[altaywtf]

Parent

#123

What this delivers

The public transition: the new app live in the App Store on both platforms, and the current app renamed as the legacy app with in-app messaging routing users to the new one.

Scope

• App Store listings for the new iOS and tvOS apps: reuse the store screenshot/marketing pipeline against the new app, listing copy, review submission. Submission sequencing per the epic's 4.3 risk note: working name → approval → rename legacy → new app takes the put.io name.
• Release lanes (beyond beta) for the new identity; release checklist per the repo's distribution docs.
• Legacy transition on main: rename the current app's display/store name to a legacy variant, add in-app messaging pointing to the new app, define the deprecation cadence (messaging intensity over time). No forced lockout ever — the legacy app keeps working, since offline libraries are not migrated. Routing messaging starts only after the new app's offline downloads (iOS offline downloads with background sessions and position sync #135) have shipped and stabilized.
• Branch flip per the epic's branch lifecycle: ship the legacy update from main first, then rename main → legacy (keep protected, releasable for emergency patches), rename next → main and set it default, and land a small PR on each branch updating workflow triggers and doc references. Optionally tag the final legacy commit.
• Re-triage the remaining open feature backlog against the new app. The product-evolution candidates adopted by Epic: Apple post-v1 product evolution — discovery, media home, and platform power #151 stay with that post-v1 epic.

Acceptance criteria

• New iOS and tvOS apps approved and live under the new identity
• Legacy app update shipped with rename + routing messaging
• Remaining backlog re-triage recorded on the epic; each open issue either retargeted, closed, or explicitly kept on legacy; Epic: Apple post-v1 product evolution — discovery, media home, and platform power #151 retains its adopted post-v1 work
• Branch flip executed: main = new app (default), legacy = old app, both protected, workflow triggers updated on both branches

Verification

Store links for both new apps; the legacy app update live; epic checklist fully green.

Blocked by

• tvOS parity pass against the shipped TV app and first TestFlight beta #144
• Completion of the Phase 1 (iOS shell) children — see the epic's delivery shape

Boundaries

No pricing/IAP changes. Removal/sunset of the legacy app is a future decision, not this issue.