[Workflows] Scope README regen to changed paths with concurrency guard

[ashleyshaw]

---

name: "🤖 Automation"
about: "Propose, fix, or improve automation (actions, scripts, bots)."
title: "[Workflows] Scope README regen to changed paths with concurrency guard"
labels: [area:workflows, v0.2.0, branding, status:needs-triage, area:automation]

Automation Summary

Update the readme-regen.yml workflow to:

• Use paths: filters to target only directories/files that have changed.
• Implement concurrency: group to ensure only one regeneration runs per target at once.
• Write only the README files affected by a given change, not all READMEs.

Steps / Checklist

• Task is clearly defined and actionable
• Automation goal and scope described
• Documentation/changelog updated
• PR uses correct branch prefix (automation/)
• Approved by at least one maintainer

Acceptance Criteria

• readme-regen.yml uses paths: filters and concurrency: group.
• Writes only affected README files.
• Automation implemented and tested
• Documentation updated
• No regressions or negative impact

Additional Context

Owner: Workflows

---

Definition of Ready (DoR)

• Automation goal/scope defined
• Checklist prepared
• Estimate added

Definition of Done (DoD)

• All checklist and acceptance criteria completed
• Documentation/changelog updated
• Approved by maintainer

---

[ashleyshaw]

Follow-up update (2026-05-27): PR #436 is merged into develop and includes this task in the execution sequence. Keeping this issue OPEN because README regen scoping/concurrency implementation work is still pending.

[ashleyshaw]

Linked under parent epic #449 ([Epic] Label governance stabilisation and automation hardening). This issue is part of the batch-01 execution set.

[ashleyshaw]

Execution update from sequence run:\n- #95 triage refresh is complete with current evidence (31 orphan labels, none applied to open issues/PRs).\n\nImpact on #67:\n- Sequencing dependency is satisfied for execution start.\n- You can proceed with README regen scoping/concurrency hardening in parallel with #66 and #69.\n\nI will keep #95 as the canonical triage source and post cross-links as implementation PRs open.