Opus finding
Concurrency group collapses unrelated workflow_dispatch runs onto a single queue key, blocking parallel skills
mediumbughigh
- .github/workflows/aeon.yml:65-67
The concurrency group key falls back to github.event.action for issues events, but for issues that's the label action name ('labeled'), so every issue-triggered run shares the group 'aeon-labeled'. With cancel-in-progress: false this serializes all 'ai-build' issue runs. Also, two simultaneous dispatches with the same skill (e.g. two different `var` values) will serialize, which contradicts the documented intent that chains run in parallel. The chain-runner relies on parallel dispatch, and serializing same-skill calls means parallel groups in chains effectively run sequentially when they target the same skill. The group key should incorporate `var` and `github.run_id` for issues to keep unrelated runs independent.
Recommendation
Include `inputs.var` (and perhaps `github.run_id` for issues events) in the concurrency group key, or scope the group by skill+var to avoid serializing independent invocations.