Downstream Subscription and Notification (Phase 2 A)

Phase: 2A
Labels: quartz, phase-2, workflow
Blocks: Phase 2 B1, Phase 2 B2
Blocked by: Phase 2 pre-A (subscriber.yml design), Phase 1 B+C (status.json published)

Context

Implement the outbound notification side of Quartz: when a relevant TheRock status
change occurs, Quartz dispatches a workflow_dispatch to each subscribed downstream
project via the Quartz Conveyor app.

Development and validation must happen against the test repository that mocks TheRock
and downstream workflows before any changes reach the production repos.

Reference: RFC-0011 (ROCm/TheRock#3728 / docs/rfcs/RFC0011-Quartz-CICD-Datahub.md in ROCm/TheRock once merged) — Phase 2, Section A.

Subissues

• Phase 2 A1: Implement Downstream Notification Workflow and Script (notify-downstream.yml, notify_subscribers.py)
• Phase 2 A2: Push Subscriber Onboarding Documentation (templates/subscriber-push.yml, docs/push-subscription.md, PR template)

Notes

• repository_dispatch may be offered as an alternative to workflow_dispatch on
  request (noted in RFC-0011 but not in scope for initial implementation).

Read RFC-0011, especially Phase 2 Section A, and review the listed subissues. Start with the test repository that mocks TheRock and downstream workflows, then inspect the planned notify-downstream.yml, notify_subscribers.py, templates/subscriber-push.yml, docs/push-subscription.md, and PR template. Done means the workflow dispatches status changes to subscribed downstream projects and the onboarding documentation is available, validated before production changes.