Clarify workflow step comment for commit ancestry verification

[Copilot]

Addresses review feedback on PR #80 requesting a more precise comment for the tag verification step in the release workflow.

The git merge-base --is-ancestor check verifies that the tagged commit is reachable from main (i.e., in main's git history), not that the tag was created directly on the main branch. This allows tags on commits from feature branches that have been merged into main.

Changes:

• Updated step name from "Ensure tag is on main" to "Verify tagged commit is in main branch history" to accurately reflect the ancestry check behavior

- name: Verify tagged commit is in main branch history
  run: |
    git fetch origin main
    if ! git merge-base --is-ancestor $GITHUB_SHA origin/main; then
      echo "Tag is not based on main. Aborting release."
      exit 1
    fi

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[mkistler]

Applied directly to #80.