Question: Can gh-aw support central label triggers across repositories?

[bbonafed]

Hi gh-aw team, quick question about CentralRepoOps trigger semantics.

For a central workflow hosted in one repository, is there any feasible path for gh-aw to provide a core trigger primitive where a label added to a pull request in another allowed repository can activate the central workflow directly?

Example desired shape:

on:
  central_pull_request_labeled:
    label: ns-pattern-review
    allowed-repos:
      - my-org/*

Intended behavior:

1. A maintainer adds ns-pattern-review to a PR in my-org/example.
2. A central workflow in my-org/central-agents activates.
3. The central workflow receives typed inputs like:
   • target_repo
   • pr_number
   • head_sha
   • base_sha
   • trigger_label
   • delivery_id
   • actor

We understand GitHub Actions events are repository-local, so this may be a GitHub platform limitation rather than something gh-aw can implement as a native trigger.

If native central label triggers are not possible, would the recommended gh-aw direction be a documented bridge pattern, such as:

• GitHub App webhook receiving pull_request.labeled
• webhook validates repo/label/PR state
• webhook dispatches the central workflow with typed inputs

Mostly trying to confirm whether this belongs as a gh-aw core trigger primitive, a documented CentralRepoOps bridge pattern, or entirely outside gh-aw.

Thanks!