fix: add shared concurrency group for gh-pages deployments

All live publish workflows now share 'gh-pages-deploy' group.
This prevents conflicts when multiple workflows deploy simultaneously.
Uses cancel-in-progress: false to queue instead of cancel.

Author: profvjreddi

.github/workflows/book-publish-live.yml

@@ -1,5 +1,10 @@
 name: '📚 Book Publish (Live)'
 
+# Shared concurrency group prevents gh-pages conflicts with other live workflows
+concurrency:
+  group: gh-pages-deploy
+  cancel-in-progress: false
+
 # =============================================================================
 # CONFIGURABLE VARIABLES - Edit these to customize the workflow
 # =============================================================================

.github/workflows/kits-publish-live.yml

@@ -10,8 +10,8 @@ permissions:
   actions: read
 
 concurrency:
-  group: kits-live-deploy
-  cancel-in-progress: true
+  group: gh-pages-deploy
+  cancel-in-progress: false
 
 jobs:
   # Build PDF first

.github/workflows/labs-publish-live.yml

@@ -10,8 +10,8 @@ permissions:
   actions: read
 
 concurrency:
-  group: labs-live-deploy
-  cancel-in-progress: true
+  group: gh-pages-deploy
+  cancel-in-progress: false
 
 jobs:
   build-and-deploy:

.github/workflows/tinytorch-publish-live.yml

@@ -12,8 +12,8 @@ permissions:
   actions: read
 
 concurrency:
-  group: tinytorch-live-deploy
-  cancel-in-progress: true
+  group: gh-pages-deploy
+  cancel-in-progress: false
 
 jobs:
   preflight: