Remove all "downstream" workflows

[strawgate]

Except for the one that looks for issues with downstream job runs

[github-actions]

TL;DR: gh-aw-downstream-users is the only removable “downstream” workflow currently in this repo, while gh-aw-downstream-health is the one to keep; I recommend deleting the downstream-users workflow stack and its data artifact, then recompiling.

Recommendation
Remove all downstream-users workflow artifacts and references, keep downstream-health, and close/supersede downstream-expansion work (like #245) unless you still want that capability under a non-downstream name.

Findings

• The issue asks to remove all downstream workflows except the one that checks downstream job runs (Remove all "downstream" workflows #263 body).
• Current downstream workflow sources in repo:
  • Keep: .github/workflows/gh-aw-downstream-health.md (description confirms health-monitoring role) at .github/workflows/gh-aw-downstream-health.md:2 and prompt body at :81-99.
  • Remove candidate: .github/workflows/gh-aw-downstream-users.md (description + prompt explicitly track downstream usage and write data/downstream-users.json) at .github/workflows/gh-aw-downstream-users.md:2, :78-84, :114-149.
• Trigger files exist for both:
  • .github/workflows/trigger-downstream-health.yml:1-16
  • .github/workflows/trigger-downstream-users.yml:1-15
• Internal-workflow docs explicitly list downstream-users as internal-only:
  • DEVELOPING.md:11
  • gh-agent-workflows/DEVELOPING.md:65
• data/downstream-users.json exists and is maintained by downstream-users workflow (data/downstream-users.json:1-43).
• Related history:
  • Create workflow to track downstream users #119 (closed via merged PR Add downstream users tracking workflow #126) created downstream-users workflow.
  • Add downstream health monitoring workflow #39 (closed) added downstream-health workflow.
  • Workflow Drift for gh-aw-release-update and gh-aw-downstream-users #235 (open) clarified downstream-users as internal-only; merged via PR Fix workflow drift for release-update and downstream-users docs #247.
  • Downstream Updates Needed workflow #245 (open) asks for additional downstream update-check workflow; draft PR [downstream] add downstream updates-needed internal workflow draft #253 was closed unmerged.
• I verified there is no active downstream-updates-needed workflow in the tree (glob **/*downstream-updates-needed* and rg downstream-updates-needed both returned no matches).

Verification

I ran local verification commands:

$ git --no-pager ls-files | grep -E 'downstream-(health|users)|downstream-users\.json'
.github/workflows/gh-aw-downstream-health.lock.yml
.github/workflows/gh-aw-downstream-health.md
.github/workflows/gh-aw-downstream-users.lock.yml
.github/workflows/gh-aw-downstream-users.md
.github/workflows/trigger-downstream-health.yml
.github/workflows/trigger-downstream-users.yml
data/downstream-users.json
gh-agent-workflows/downstream-health/README.md
gh-agent-workflows/downstream-health/example.yml

$ make compile
... 
✓ .github/workflows/gh-aw-downstream-health.md
✓ .github/workflows/gh-aw-downstream-users.md
⚠ Compiled 32 workflow(s): 0 error(s), 11 warning(s)

$ glob "**/*downstream-updates-needed*"
No files matched the pattern.

$ rg "downstream-updates-needed" .
No matches found.

Detailed Action Plan

1. Delete downstream-users workflow source + compiled artifact + trigger:
   • .github/workflows/gh-aw-downstream-users.md
   • .github/workflows/gh-aw-downstream-users.lock.yml
   • .github/workflows/trigger-downstream-users.yml
2. Remove the generated data file that only this workflow maintains:
   • data/downstream-users.json
3. Update docs that currently mention downstream-users as internal-only:
   • DEVELOPING.md:11
   • gh-agent-workflows/DEVELOPING.md:65
4. Re-run compile/lint to ensure consistency after workflow deletion:
   • make compile
   • make lint
5. Keep downstream-health untouched:
   • .github/workflows/gh-aw-downstream-health.md and .github/workflows/trigger-downstream-health.yml
   • gh-agent-workflows/downstream-health/*
6. Follow-up issue hygiene:
   • Decide whether Downstream Updates Needed workflow #245 should be closed as not planned (or renamed/reframed if the capability is still desired without “downstream” workflows).

Related Items

Type	Link	Relevance
Issue	#263	Current request
Issue	#119	Introduced downstream-users requirement
PR	#126	Merged implementation of downstream-users
Issue	#39	Added downstream-health workflow
Issue	#235	Documented downstream-users internal-only status
PR	#247	Merged docs/source drift fix including downstream-users docs
Issue	#245	Open request for additional downstream workflow; potentially conflicts with removal direction
PR	#253	Closed/unmerged downstream-updates-needed draft
File	.github/workflows/gh-aw-downstream-health.md:2,81-99	Keep this downstream workflow
File	.github/workflows/gh-aw-downstream-users.md:2,78-84,114-149	Primary removal target
File	.github/workflows/trigger-downstream-users.yml:1-15	Trigger to remove
File	data/downstream-users.json:1-43	Data artifact produced by downstream-users

---

What is this? | From workflow: Issue Triage Agent

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #263

[strawgate]

/ai make a pr

[github-actions]

Implemented and opened a PR that removes the downstream-users artifact and cleans docs references.

Included in the PR

• Deleted data/downstream-users.json
• Removed gh-aw-downstream-users.md mention from DEVELOPING.md
• Removed gh-aw-downstream-users internal-workflow note from gh-agent-workflows/DEVELOPING.md

Validation run

• make compile
• make lint

To fully close #263, a maintainer still needs to remove these restricted workflow files under .github/workflows/:

• gh-aw-downstream-users.md
• gh-aw-downstream-users.lock.yml
• trigger-downstream-users.yml

---

What is this? | From workflow: Issue Assistant

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #263