Split tag-driven desktop release from manual iOS TestFlight release

[Copilot]

What Changed

Release tags now drive the desktop/CLI release path only. iOS TestFlight is dispatched separately, while still targeting the same release version/ref for backfills such as v0.26.0.

• Workflow split

  • Removed tag-push triggering from .github/workflows/release-ios.yml
  • Kept workflow_dispatch and added optional ref input
  • Defaulted manual iOS runs to refs/tags/v<version> so a release can be rebuilt from the tagged commit instead of current branch head
  • Resolved and propagated the checked-out commit SHA through preflight for clearer release metadata

• Release docs and runbook

  • Updated docs/release.md and README.md to describe the desktop/CLI tag release and separate iOS dispatch
  • Updated scripts/prepare-release.ts text generation so future release notes/manifests/checklists match the new flow
  • Updated docs/releases/v0.26.0* rollout guidance to trigger release-ios.yml manually for that release

on:
  workflow_dispatch:
    inputs:
      version:
        required: true
      ref:
        required: false

Why

Desktop/CLI publication should not be coupled to iOS signing/TestFlight readiness or retry behavior. Separating the iOS lane keeps the release tag path deterministic while preserving a clean way to promote or backfill the matching mobile build from v0.26.0 or any later tag.

UI Changes

None.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
okcode-marketing	Ready	Preview	Apr 20, 2026 7:43pm
v0-compute-the-platform-to-build	Ready	Preview, Open in v0	Apr 20, 2026 7:43pm