[autonomy-atomicity] Duplicated workflow registries in setup/dispatch scripts create a merge-conflict hotspot

[github-actions]

Autonomy / Atomicity Findings

1. Duplicated hard-coded workflow registries across setup and dispatch scripts

Category: Manual routing | Config hotspot
File(s):

• scripts/trigger-ci-workflows.sh (workflow/category registries and routing): lines 18-46, 88-94, 138-142
• scripts/quick-setup.sh (recommended workflow registries): lines 121-142, 148, 162-166

Problem:
Two separate scripts hard-code overlapping workflow inventories and categories. Adding or reclassifying workflows requires touching central arrays and switch logic in multiple places. In parallel development, unrelated PRs frequently target these same blocks, which increases merge conflicts and makes dropped/partial updates more likely.

This is not just centralization by design: the same concern (workflow set definition) is duplicated across multiple files with manual synchronization requirements.

Suggested fix:
Introduce a single source of truth for workflow metadata (for example, a manifest generated from gh-agent-workflows/* metadata or a dedicated machine-readable registry file), then have both scripts read from that source instead of maintaining separate arrays and category switches.

Suggested Actions

• Define one canonical workflow metadata source (name, category, recommended set flags).
• Refactor scripts/trigger-ci-workflows.sh to load categories/workflows from that source.
• Refactor scripts/quick-setup.sh to build default/recommended sets from the same source.
• Add a validation check in CI to fail when script-visible workflow sets diverge from the canonical source.

Note

🔒 Integrity filtering filtered 1 item

Integrity filtering activated and filtered the following item during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.

• issue:elastic/ai-github-actions#unknown (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)

---

What is this? | From workflow: Trigger Autonomy Atomicity Analyzer

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.