Fix Pages deployment by switching to GitHub Actions deploy.

Replace mkdocs gh-deploy with upload-pages-artifact and deploy-pages to avoid conflicting with the automatic pages-build-deployment workflow that was cancelling legacy branch deploys.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: Markus Koch

.github/workflows/gh-pages.yml

@@ -10,6 +10,15 @@ on:
     branches:
       - main
 
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: false
+
 jobs:
   build:
     runs-on: ubuntu-latest
@@ -20,15 +29,17 @@ jobs:
           python-version: "3.12"
       - run: pip install -r requirements.txt
       - run: mkdocs build --strict
+      - uses: actions/upload-pages-artifact@v3
+        with:
+          path: site
 
   deploy:
     if: github.event_name == 'push' && github.ref == 'refs/heads/main'
     needs: build
     runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
     steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-python@v5
-        with:
-          python-version: "3.12"
-      - run: pip install -r requirements.txt
-      - run: mkdocs gh-deploy --force
+      - id: deployment
+        uses: actions/deploy-pages@v4