Release Notes Draft

Generates a markdown draft of the impending Warp release's GitHub release notes, written in GitHub Flavored Markdown. Auto-detects feature vs bugfix release from the version, picks the correct prior tag for diffing, and produces a digestible user-facing summary that the release manager edits and posts to the release page.

Output: a single markdown report, filed according to the destination chosen in Phase 1:

• Secret gist (default when gh is available and authenticated): stable filename warp-<version-string>-release-notes.md, stable description Warp <version-string> Release Notes Draft. Later runs against the same version revise the same gist in place; prior versions are preserved in the gist's git history.
• Local markdown file (fallback when gh unavailable, or opt-in when gh available): dated path at $(pwd)/warp-<version-string>-release-notes-<YYYY-MM-DD>.md. Not auto-committed; the user reviews, edits, and copy-pastes into the GitHub release form.

Inputs: the positional argument is a branch name (resolved as upstream/<name> → origin/<name> → local), a tag (e.g. v1.13.0), or omitted (defaults to HEAD). Version string comes from VERSION.md at the resolved head, or parsed from the tag name.

Phase 1 — Resolve target and previous release

1. Resolve the head ref. With no argument, head = HEAD. With an argument, try in order: upstream/<arg>, origin/<arg>, <arg> (local branch or tag). Use the first that resolves via git rev-parse --verify <candidate>. Record both the symbolic ref and the resolved SHA. If nothing resolves, abort with the candidate list shown.