[bug-hunter] Release update workflow lock file missing

[github-actions]

Impact

Users installing the Release Update Check workflow from gh-agent-workflows/release-update will get a runtime failure because the referenced lock workflow (.github/workflows/gh-aw-release-update.lock.yml) is not present in the repository.

Reproduction Steps

1. From the repo root, run:

ls -l .github/workflows/gh-aw-release-update.lock.yml .github/workflows/gh-aw-release-update.md github/workflows/gh-aw-release-update.md

Expected vs Actual

Expected: .github/workflows/gh-aw-release-update.lock.yml (and its source .md) exist because gh-agent-workflows/release-update/example.yml references them.

Actual:

ls: cannot access '.github/workflows/gh-aw-release-update.lock.yml': No such file or directory
ls: cannot access '.github/workflows/gh-aw-release-update.md': No such file or directory
-rw-r--r-- 1 runner runner 3927 Feb 19 11:20 github/workflows/gh-aw-release-update.md

Suggested Failing Test

Add a lint check that asserts every gh-agent-workflows/*/example.yml uses: reference under .github/workflows/gh-aw-*.lock.yml exists on disk (this would fail for release-update today).

Evidence

• gh-agent-workflows/release-update/example.yml:14 references elastic/ai-github-actions/.github/workflows/gh-aw-release-update.lock.yml@v0
• The only source file present is github/workflows/gh-aw-release-update.md (missing the leading dot), so no compiled lock file is generated under .github/workflows/

---

What is this? | From workflow: Gh Aw Bug Hunter

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

• expires on Feb 26, 2026, 11:26 AM UTC