fix(ci): push automated data commits with BOT_TOKEN

The daily-update / weekly-digest jobs pushed with the default GITHUB_TOKEN
(github-actions[bot]), which the 'main' ruleset rejected ('repository rule
violations') since the bot is not a bypass actor — so no track data had been
committed since initial setup. Persist the BOT_TOKEN PAT (whose admin owner is
in the ruleset's Repository-admin bypass list) via actions/checkout instead.

This also lets the data commits trigger deploy-pages: pushes made with
GITHUB_TOKEN are suppressed by GitHub's workflow-recursion guard, so the site
previously never refreshed after a data commit.

Author: kanywst

.github/workflows/daily-update.yml

@@ -24,6 +24,12 @@ jobs:
           # Pin to main so a workflow_dispatch from a feature branch can't
           # publish data based on non-main code (the commit still lands on main).
           ref: main
+          # Persist a PAT (admin owner) instead of GITHUB_TOKEN so the later
+          # push (a) bypasses the `main` ruleset via the Repository-admin bypass
+          # actor, and (b) triggers deploy-pages — GITHUB_TOKEN pushes are
+          # suppressed by GitHub's workflow-recursion guard, so the site would
+          # otherwise never refresh after a data commit.
+          token: ${{ secrets.BOT_TOKEN }}
       - uses: actions/setup-python@v6
         with:
           python-version: '3.12'

.github/workflows/weekly-digest.yml

@@ -24,6 +24,12 @@ jobs:
           # Pin to main so a workflow_dispatch from a feature branch can't
           # publish a digest built from non-main code.
           ref: main
+          # Persist a PAT (admin owner) instead of GITHUB_TOKEN so the later
+          # push (a) bypasses the `main` ruleset via the Repository-admin bypass
+          # actor, and (b) triggers deploy-pages — GITHUB_TOKEN pushes are
+          # suppressed by GitHub's workflow-recursion guard, so the site would
+          # otherwise never refresh after a digest commit.
+          token: ${{ secrets.BOT_TOKEN }}
       - uses: actions/setup-python@v6
         with:
           python-version: '3.12'