Use RELEASE_PAT in release workflow to trigger CI (#119)

## Summary
- Release PRs created by the bot never had CI checks run because
`GITHUB_TOKEN` events don't trigger downstream workflows (GitHub
anti-recursion policy)
- Switch to `RELEASE_PAT` so the push and PR creation events trigger CI
and summary workflows normally
- This unblocks release PRs like #118 from being stuck on missing
`required-checks`

## Test plan
- [ ] Verify next release PR (via workflow_dispatch) triggers CI and
summary checks
- [ ] Confirm `required-checks` status appears on the release PR

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

Author: coreymartin

.github/workflows/release.yaml

@@ -113,13 +113,18 @@ jobs:
       - name: Create release branch and PR
         if: github.event_name == 'workflow_dispatch'
         env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          # Use a PAT so the push and PR creation trigger CI workflows.
+          # GITHUB_TOKEN events don't trigger workflows (GitHub anti-recursion).
+          GH_TOKEN: ${{ secrets.RELEASE_PAT }}
         run: |
           OLD_VERSION="${{ steps.changes.outputs.old_version }}"
           NEW_VERSION="${{ steps.bump.outputs.new_version }}"
           VERSION_BUMP="${{ steps.ai.outputs.version_bump }}"
           BRANCH="release/v${NEW_VERSION}"
 
+          # Configure git to push with the PAT
+          git remote set-url origin "https://x-access-token:${GH_TOKEN}@github.com/${{ github.repository }}.git"
+
           git checkout -b "$BRANCH"
           git add package.json package-lock.json CHANGELOG.md
           git commit -m "v${NEW_VERSION}"