15 changed files with 15 additions and 15 deletions
@@ -57,7 +57,7 @@ permissions:
 # can produce duplicate comments before the title-search dedup wins.
 concurrency:
  group: ci-required-drift
-  cancel-in-progress: false
+  cancel-in-progress: true

 jobs:
  drift:
@@ -92,7 +92,7 @@ permissions:
 # stacking up.
 concurrency:
  group: continuous-synth-e2e
-  cancel-in-progress: false
+  cancel-in-progress: true

 env:
  GITHUB_SERVER_URL: https://git.moleculesai.app
@@ -101,7 +101,7 @@ concurrency:
  # See e2e-staging-canvas.yml's identical concurrency block for the full
  # rationale and the 2026-04-28 incident reference.
  group: e2e-api-${{ github.event.pull_request.head.sha || github.sha }}
-  cancel-in-progress: false
+  cancel-in-progress: true

 env:
  GITHUB_SERVER_URL: https://git.moleculesai.app
@@ -32,7 +32,7 @@ on:

 concurrency:
  group: e2e-chat-${{ github.event.pull_request.head.sha || github.sha }}
-  cancel-in-progress: false
+  cancel-in-progress: true

 env:
  GITHUB_SERVER_URL: https://git.moleculesai.app
@@ -15,7 +15,7 @@ on:

 concurrency:
  group: e2e-legacy-advisory
-  cancel-in-progress: false
+  cancel-in-progress: true

 permissions:
  contents: read
@@ -115,7 +115,7 @@ concurrency:
  # would let a queued staging/main push behind a PR run get cancelled,
  # leaving any gate that reads "completed run at SHA" stuck.
  group: e2e-peer-visibility-${{ github.event.pull_request.head.sha || github.sha }}
-  cancel-in-progress: false
+  cancel-in-progress: true

 env:
  GITHUB_SERVER_URL: https://git.moleculesai.app
@@ -62,7 +62,7 @@ concurrency:
  # wasted CI is acceptable given the alternative is losing staging-tip
  # data that auto-promote-staging needs.
  group: e2e-staging-canvas-${{ github.event.pull_request.head.sha || github.sha }}
-  cancel-in-progress: false
+  cancel-in-progress: true

 env:
  GITHUB_SERVER_URL: https://git.moleculesai.app
@@ -26,7 +26,7 @@ env:

 concurrency:
  group: e2e-staging-sanity
-  cancel-in-progress: false
+  cancel-in-progress: true

 permissions:
  issues: write
@@ -69,7 +69,7 @@ on:
    branches: [main, staging]
 concurrency:
  group: handlers-pg-integ-${{ github.event.pull_request.head.sha || github.sha }}
-  cancel-in-progress: false
+  cancel-in-progress: true

 env:
  GITHUB_SERVER_URL: https://git.moleculesai.app
@@ -54,7 +54,7 @@ concurrency:
  # cancellation deadlock — see e2e-api.yml's concurrency block for
  # the 2026-04-28 incident that codified this pattern.
  group: harness-replays-${{ github.event.pull_request.head.sha || github.sha }}
-  cancel-in-progress: false
+  cancel-in-progress: true

 env:
  GITHUB_SERVER_URL: https://git.moleculesai.app
@@ -40,7 +40,7 @@ env:

 concurrency:
  group: railway-pin-audit
-  cancel-in-progress: false
+  cancel-in-progress: true

 permissions:
  issues: write
@@ -50,7 +50,7 @@ on:
 # Don't let two sweeps race the same AWS account.
 concurrency:
  group: sweep-aws-secrets
-  cancel-in-progress: false
+  cancel-in-progress: true

 permissions:
  contents: read
@@ -58,7 +58,7 @@ on:
 # scheduled run would otherwise issue duplicate DELETE calls.
 concurrency:
  group: sweep-cf-orphans
-  cancel-in-progress: false
+  cancel-in-progress: true

 permissions:
  contents: read
@@ -42,7 +42,7 @@ on:
 # Don't let two sweeps race the same account.
 concurrency:
  group: sweep-cf-tunnels
-  cancel-in-progress: false
+  cancel-in-progress: true

 permissions:
  contents: read
@@ -51,7 +51,7 @@ on:
 # on a manual trigger; queue rather than parallel-delete.
 concurrency:
  group: sweep-stale-e2e-orgs
-  cancel-in-progress: false
+  cancel-in-progress: true

 permissions:
  contents: read