gh-aw-release-update — Missing source file
There is a gh-aw-release-update.lock.yml and trigger-release-update.yml in .github/workflows/, and a gh-agent-workflows/release-update/ directory with example.yml and README.md. However, there is no gh-aw-release-update.md source file. The lock file exists but its source is missing from the repo. This means it cannot be recompiled locally and will drift silently.
gh-aw-downstream-users — Missing consumer directory
gh-aw-downstream-users.md and .lock.yml exist in .github/workflows/, along with trigger-downstream-users.yml, but there is no gh-agent-workflows/downstream-users/ directory — no consumer-facing example.yml or README.md. This workflow is effectively internal-only but isn't documented as such (unlike gh-aw-upgrade-check, which is explicitly called out as internal in DEVELOPING.md).
gh-aw-release-update — Missing source file
There is a gh-aw-release-update.lock.yml and trigger-release-update.yml in .github/workflows/, and a gh-agent-workflows/release-update/ directory with example.yml and README.md. However, there is no gh-aw-release-update.md source file. The lock file exists but its source is missing from the repo. This means it cannot be recompiled locally and will drift silently.
gh-aw-downstream-users — Missing consumer directory
gh-aw-downstream-users.md and .lock.yml exist in .github/workflows/, along with trigger-downstream-users.yml, but there is no gh-agent-workflows/downstream-users/ directory — no consumer-facing example.yml or README.md. This workflow is effectively internal-only but isn't documented as such (unlike gh-aw-upgrade-check, which is explicitly called out as internal in DEVELOPING.md).