[agent-suggestions] Agent suggestions - 2026-08-10

[github-actions]

Agent Suggestions

Date: 2026-08-10

1. workflow-adoption-drift-detector

Trigger: Weekly schedule + workflow_dispatch
Purpose: Detect downstream adoption drift for elastic/ai-github-actions consumers: deprecated uses: targets, disabled trigger jobs (if: false), and missing branch-resident workflow parity across active maintenance/backport branches.
Proposed safe outputs: create-issue (single consolidated report with affected repos/branches + remediation checklist)
Evidence:

• elastic/integrations #19262 — branch-resident workflow migration gap on active backport branches: backport: deploy backport-branch automation workflows to active backport branches integrations#19262
• elastic/integrations #19321 — missing self-service retry automation path for changelog sync failures: [CI] Add /sync-changelog comment trigger to retry failed changelog sync PRs integrations#19321
• elastic/logstash repetitive backport workflow PRs for the same CI change: #19307, #19308, #19309, #19310
  • [9.5] (backport #19278) CI: Add OpenAPI spec lint and S3 publish workflows logstash#19307
  • [9.4] (backport #19278) CI: Add OpenAPI spec lint and S3 publish workflows logstash#19308
  • [9.3] (backport #19278) CI: Add OpenAPI spec lint and S3 publish workflows logstash#19309
  • [8.19] (backport #19278) CI: Add OpenAPI spec lint and S3 publish workflows logstash#19310
• Downstream trigger drift examples in workflow files:
  • Deprecated alias still in use: elastic/beats/.github/workflows/trigger-breaking-change-detect.yml uses gh-aw-breaking-change-detect.lock.yml@v0
  • Deprecated alias still in use: elastic/elastic-agent/.github/workflows/trigger-breaking-change-detect.yml uses gh-aw-breaking-change-detect.lock.yml@v0
  • Disabled AI workflow trigger: elastic/integrations/.github/workflows/trigger-stale-issues.yml (if: false)
    Why not covered already:
• release-update updates pinned workflow SHAs, but does not audit deprecated aliases, disabled triggers, or branch workflow parity.
• internal-downstream-health monitors bot output quality/silence, but does not audit workflow adoption/configuration drift.

Duplicate Checks

• Open issues reviewed: repo:elastic/ai-github-actions is:issue is:open (agent OR workflow OR automation)
• Open PRs reviewed: repo:elastic/ai-github-actions is:pr is:open (agent OR workflow)
• Prior reports reviewed: repo:elastic/ai-github-actions is:issue in:title "[agent-suggestions]"
• Existing open suggestion [agent-suggestions] Agent suggestions - 2026-08-03 #1746 is focused on PR lifecycle hygiene, not downstream adoption drift: [agent-suggestions] Agent suggestions - 2026-08-03 #1746

Downstream Signals

• elastic/integrations: #19262, #19321
• elastic/logstash: #19307, #19308, #19309, #19310
• elastic/beats: deprecated trigger alias in .github/workflows/trigger-breaking-change-detect.yml
• elastic/elastic-agent: deprecated trigger alias in .github/workflows/trigger-breaking-change-detect.yml

Suggested Next Steps

• Prototype gh-aw-workflow-adoption-drift-detector as a scheduled-audit workflow that emits one deduplicated issue with repo/branch drift findings and fix checklist.

---

What is this? | From workflow: Trigger Agent Suggestions

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

• expires on Aug 17, 2026, 12:45 PM UTC

[github-actions]

This issue was automatically closed because it expired on 2026-08-17T12:45:02.905Z.

Closed by Workflow