fix(ci): use PAT token for dev release pushes

- align dev-release workflow with protected-branch bypass used by release.yml

- add a workflow regression test so checkout and release auth do not drift back to github.token

.github/workflows/dev-release.yml

@@ -26,8 +26,9 @@ jobs:
         with:
           fetch-depth: 0
           ref: dev
-          # Always use the built-in workflow token; PAT rotation/breakage must not block dev releases.
-          token: ${{ github.token }}
+          # PAT_TOKEN required: dev-release pushes version bump commits to dev,
+          # and protected branches reject github.token writes once status checks are required.
+          token: ${{ secrets.PAT_TOKEN }}
 
       - name: Setup Bun
         uses: oven-sh/setup-bun@v2
@@ -58,10 +59,10 @@ jobs:
         id: release
         env:
           HUSKY: 0
-          # Use built-in GITHUB_TOKEN for release + issue operations.
-          # Checkout credentials are resolved above with PAT fallback.
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          # PAT_TOKEN bypasses branch protection so the workflow can push
+          # the dev release commit and tag back to the protected dev branch.
+          GITHUB_TOKEN: ${{ secrets.PAT_TOKEN }}
+          GH_TOKEN: ${{ secrets.PAT_TOKEN }}
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
         run: |