fix: encapsulate draft releases into public updates

Author: Spelkington

.github/agents/dev-relations.agent.md

@@ -21,9 +21,9 @@ These inform how you frame changes. A new analyzer is not just "a new analyzer"
 <workflow>
 Follow these steps in order:
 
-1. **Identify the last two tags.** Run `git tag --sort=-v:refname | head -2`.
-2. **Gather raw changes.** Run `git log <old-tag>..<new-tag> --oneline` and read the corresponding section of `/CHANGELOG.md`.
-3. **Inspect changes by area.** Run `git diff <old-tag>..<new-tag> --stat` to see which files changed. When a commit message is unclear, read the actual diff or changed files to understand what happened.
+1. **Determine the tag range.** The prompt may specify a base tag and a head tag (e.g., "base: v0.1.35, head: v0.1.38"). If provided, use those directly. Otherwise, identify the latest tag with `git tag --sort=-v:refname | head -1` as the head, and the second-latest with `head -2 | tail -1` as the base.
+2. **Gather raw changes.** Run `git log <base-tag>..<head-tag> --oneline` and read all corresponding sections of `/CHANGELOG.md` that fall within the range — there may be multiple version entries if several releases occurred since the last published release.
+3. **Inspect changes by area.** Run `git diff <base-tag>..<head-tag> --stat` to see which files changed. When a commit message is unclear, read the actual diff or changed files to understand what happened.
 4. **Identify the topology.** Determine the single most impactful user-facing change — the headline. Everything else in the release either supports that headline (examples demonstrating it, docs explaining it) or is independent. This topology drives the structure of the summary.
 5. **Categorize changes** using these rules:
    - `src/` — Library changes. Frame as user-facing improvements: new capabilities, better error messages, stability gains. Connect to Flowthru's core promises where natural.

.github/workflows/release.yml

@@ -147,12 +147,30 @@ jobs:
         if: steps.release.outputs.changed == 'true'
         run: npm install -g @github/copilot
 
+      - name: Determine last published release tag
+        if: steps.release.outputs.changed == 'true'
+        id: last-published
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          # Find the most recent non-draft, non-prerelease published release tag
+          BASE_TAG=$(gh release list --limit 20 --json tagName,isDraft,isPrerelease \
+            --jq '[.[] | select(.isDraft == false and .isPrerelease == false)] | .[0].tagName // empty')
+          if [ -z "$BASE_TAG" ]; then
+            # Fallback: second-latest git tag if no published release exists
+            BASE_TAG=$(git tag --sort=-v:refname | head -2 | tail -1)
+          fi
+          echo "tag=${BASE_TAG}" >> $GITHUB_OUTPUT
+          echo "Base tag for release summary: ${BASE_TAG}"
+
       - name: Generate release summary
         if: steps.release.outputs.changed == 'true'
         env:
           COPILOT_GITHUB_TOKEN: ${{ secrets.COPILOT_CLI_TOKEN }}
         run: |
-          copilot -p "Generate a release summary for the latest release." \
+          HEAD_TAG="v${{ steps.release.outputs.version }}"
+          BASE_TAG="${{ steps.last-published.outputs.tag }}"
+          copilot -p "Generate a release summary. Base tag: ${BASE_TAG}, head tag: ${HEAD_TAG}. Summarize all changes between these two tags." \
             --agent=dev-relations \
             --available-tools='view,create,bash' \
             --allow-tool='shell(git:*)' \