Fix concurrent Pages deployment causing duplicate artifact error

cancel-in-progress: true ensures a newer run cancels the previous
in-progress one instead of both uploading a "github-pages" artifact
concurrently, which triggers the "artifact count is 2" deploy error.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: manugarg

.github/workflows/deploy-pages.yml

@@ -15,11 +15,12 @@ permissions:
   pages: write
   id-token: write
 
-# Only one Pages deployment at a time; skip queued runs but don't cancel
-# an in-progress deploy.
+# Only one Pages deployment at a time. Cancel any in-progress run when a
+# newer one starts, preventing the "multiple github-pages artifacts" error
+# that occurs when two runs both reach the upload step concurrently.
 concurrency:
   group: pages
-  cancel-in-progress: false
+  cancel-in-progress: true
 
 jobs:
   deploy: