elastic / elastic/ai-github-actions
[autonomy-atomicity] Recommended workflow sets are duplicated across installer and docs, creating drift and merge hotspots
- Dominant language
- Python
- Stars
- 11
- Forks
- 16
- Avg merge
- 22h 9m
- Merged PRs (30d)
- 31
Description
## Autonomy / Atomicity Findings
### 1. Recommended workflow set definitions are duplicated and already drifting
**Category:** Manual routing/registration | Config hotspot
**File(s):** `scripts/quick-setup.sh:128-142`, `README.md:25-26`, `docs/workflows/gh-agent-workflows.md:28-29`, `gh-agent-workflows/README.md:67-80`
**Problem:**
The "continuous improvement" recommended set is maintained in multiple places. The installer script includes `product-manager-impersonator` and `refactor-opportunist` (`scripts/quick-setup.sh:134-135`), while top-level docs omit them (`README.md:26`, `docs/workflows/gh-agent-workflows.md:29`).
This creates a parallel-change blocker: adding/removing recommended workflows requires synchronized edits across several central files, increasing merge-conflict risk and causing silent behavior/documentation drift when one update is missed.
**Suggested fix:**
Create one canonical machine-readable manifest for workflow sets (for example under `gh-agent-workflows/`), then generate or validate both:
- installer arrays (`scripts/quick-setup.sh`)
- docs snippets (`README.md`, `docs/workflows/gh-agent-workflows.md`, `gh-agent-workflows/README.md`)
Add CI validation that fails when rendered docs/installer sets diverge from the canonical source.
## Suggested Actions
- [ ] Introduce a single source of truth for recommended workflow sets.
- [ ] Refactor `scripts/quick-setup.sh` to consume generated/validated set data.
- [ ] Update docs generation/validation so all recommended-set docs are derived from the same source.
- [ ] Add a CI check that detects recommended-set drift across script and docs.
> [!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?](https://ela.st/github-ai-tools) | [From workflow: Trigger Autonomy Atomicity Analyzer](https://github.com/elastic/ai-github-actions/actions/runs/23808168815)
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
Contributor guide
Assessment
This issue has not been assessed yet.