From the #569 merge digest (control tower). The Queues section hardcodes the four queue labels (priority: needs-triage, status: ready, status: needs-decision, needs-human); a consuming repo with a different labeling scheme sees 0/? counts. The telemetry-issue path already demonstrates the right pattern (auto-discover, degrade gracefully when absent) — apply the same to the queue label set (configurable or degrade).
Portability-coupling class — likely folds into #531's lint-lane scope at triage.
Filed by the control-tower session from a merge-digest finding.
From the #569 merge digest (control tower). The Queues section hardcodes the four queue labels (
priority: needs-triage,status: ready,status: needs-decision,needs-human); a consuming repo with a different labeling scheme sees 0/? counts. The telemetry-issue path already demonstrates the right pattern (auto-discover, degrade gracefully when absent) — apply the same to the queue label set (configurable or degrade).Portability-coupling class — likely folds into #531's lint-lane scope at triage.
Filed by the control-tower session from a merge-digest finding.