Mention the Playground in docs

[strawgate]

https://github.com/elastic/ai-github-actions-playground

and elastic/beats and elastic/integrations and strawgate/py-key-value

[github-actions]

1 related issue

• Downstream Updates Needed workflow #245 — it tracks downstream repositories in the same org scope and includes concrete downstream inventory context that can inform which external repos should be called out in this issue’s docs update.

---

What is this? | From workflow: Duplicate Issue Detector

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

[github-actions]

TL;DR: this issue is valid, and the cleanest fix is to document the requested repos as explicit downstream examples and update the Downstream Health prompt’s seeded repo list so elastic/ai-github-actions-playground, elastic/beats, elastic/integrations, and strawgate/py-key-value are clearly covered.

Recommendation

Add a “known downstream/example repositories” list in docs and align the Downstream Health workflow prompt with that same list.
Concretely: update .github/workflows/gh-aw-downstream-health.md (source of runtime behavior) and gh-agent-workflows/downstream-health/README.md / docs listing so users can discover those repos from documentation, not only from implicit search behavior.

Findings

• The issue asks to mention these repos in docs: elastic/ai-github-actions-playground, elastic/beats, elastic/integrations, strawgate/py-key-value.
• Current Downstream Health prompt only seeds two repos:
  • .github/workflows/gh-aw-downstream-health.md:99-102 → elastic/integrations, elastic/infra-party
  • .github/workflows/gh-aw-downstream-health.md:165-167 repeats those in the report template.
• No playground mention exists anywhere in the repo at the moment (search result: no matches).
• Public docs currently list Downstream Health only as a one-line catalog entry (docs/workflows/gh-agent-workflows.md:84) with no seeded repo examples.
• Related context:
  • Add downstream health monitoring workflow #39 introduced Downstream Health with the same original seeded repos (elastic/integrations, elastic/infra-party).
  • Let's add workflows for refactor and new features #359 and draft PR Add product-manager-impersonator and refactor-opportunist workflows #360 already reference the playground pattern for workflow ideation, but they do not resolve this docs request directly.

Verification

I verified current mentions locally:

$ grep -RInE "playground|elastic/integrations|elastic/beats|py-key-value" docs gh-agent-workflows/downstream-health/README.md .github/workflows/gh-aw-downstream-health.md || true
.github/workflows/gh-aw-downstream-health.md:100:   - elastic/integrations
.github/workflows/gh-aw-downstream-health.md:165:> - elastic/integrations

And repo-wide search for playground returned no matches.

Detailed Action Plan

1. Update downstream workflow source prompt

   • Edit .github/workflows/gh-aw-downstream-health.md:
     • Expand “Known repos include” at :99-102 to include:
       • elastic/ai-github-actions-playground
       • elastic/beats
       • elastic/integrations (already present)
       • strawgate/py-key-value
     • Mirror the same list in the “Monitored Repositories” example block at :163-167.

2. Clarify discovery behavior for non-Elastic repos

   • In the same file near :94-97, keep org:elastic discovery for broad scanning, but add explicit wording that the seeded list includes manually monitored repos outside org:elastic (for strawgate/py-key-value).

3. Update user-facing docs

   • Add a short “Example downstream repos” section in gh-agent-workflows/downstream-health/README.md after “How it works” (:5-8).
   • Optionally append one sentence to docs/workflows/gh-agent-workflows.md near the Downstream Health row (:84) pointing readers to that README section.

4. Regenerate compiled artifacts (if any synced files are affected)

   • Run make compile and then make lint to ensure prompt/lock consistency and no workflow lint regressions.

5. Sanity check output wording

   • Ensure issue/report template language does not imply all repos are Elastic-owned once strawgate/py-key-value is included.

Related Items

Type	Link	Relevance
Issue	#361	Current request
Issue	#39	Original downstream-health introduction and seeded repo list
Issue	#359	Related workflow discussion referencing playground pattern
PR	#360 (draft)	Adds ideas/refactor workflows; references playground pattern
File	.github/workflows/gh-aw-downstream-health.md:94-102	Repo discovery + seeded list
File	.github/workflows/gh-aw-downstream-health.md:163-167	Report template monitored repos
File	gh-agent-workflows/downstream-health/README.md:5-8	User-facing workflow behavior description
File	docs/workflows/gh-agent-workflows.md:84	Current one-line Downstream Health docs entry
Web	https://github.com/elastic/ai-github-actions-playground	Repo requested to be documented
Web	https://github.com/elastic/beats	Repo requested to be documented
Web	https://github.com/elastic/integrations	Repo requested to be documented
Web	https://github.com/strawgate/py-key-value	Repo requested to be documented

---

What is this? | From workflow: Issue Triage

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

[strawgate]

Let's organize into heavy medium and light users and let's highlight the playground specifically