From 1d9a75f71c882303f9be4a96bc21699b456b8de1 Mon Sep 17 00:00:00 2001
From: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com>
Date: Fri, 26 Jun 2026 22:08:30 +0000
Subject: [PATCH] =?UTF-8?q?feat:=20implement=20issue=20#395=20=E2=80=94=20?=
 =?UTF-8?q?Compliance:=20dev-lead-stub-concurrency?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 .github/workflows/dev-lead.yml | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/dev-lead.yml b/.github/workflows/dev-lead.yml
index 0eb8c7f..107d265 100644
--- a/.github/workflows/dev-lead.yml
+++ b/.github/workflows/dev-lead.yml
@@ -37,12 +37,17 @@ on:
 
 permissions: {}
 
-concurrency:
-  group: dev-lead
-  cancel-in-progress: false
+# Concurrency is centralised in the reusable workflow (dev-lead-reusable.yml) with
+# per-issue / per-PR lanes, so issue pickups are never cancelled by PR follow-up
+# traffic and the grouping can't drift per-repo. See petry-projects/.github#402.
 
 jobs:
   dev-lead:
+    # Pinned to the moving dev-lead/stable channel tag, not @main, so a broken
+    # change to dev-lead can no longer gate its own fix (the self-host circular
+    # dependency). Promotion is done by moving the dev-lead/stable tag centrally; this
+    # caller is never edited on release. agent_ref threads the same channel into
+    # dev-lead's own scripts/prompts checkout. See ci-standards.md#dev-lead-agent.
     uses: petry-projects/.github-private/.github/workflows/dev-lead-reusable.yml@dev-lead/stable
     with:
       agent_ref: dev-lead/stable
@@ -53,4 +58,4 @@ jobs:
       issues: write
       actions: read
       checks: read
-      statuses: read # required by dev-lead-reusable.yml since #435
+      statuses: read