Fix campaign orchestrator tracker label convention: campaign: → z_campaign_

[Copilot]

Campaign orchestrator was using campaign:security-alert-burndown label convention, yielding 0 discovery matches. Discovery script generates and searches for z_campaign_<campaign-id> labels, and worker workflows tag items with this prefix.

Changes

• Campaign spec (.github/workflows/security-alert-burndown.campaign.md): Updated tracker-label from campaign:security-alert-burndown → z_campaign_security-alert-burndown

• Validation (pkg/campaign/validation.go): Enforces z_campaign_ prefix instead of campaign: prefix

  // Before: validated "campaign:" prefix
  if !strings.HasPrefix(trimmedLabel, "campaign:") {
  
  // After: validates "z_campaign_" prefix matching auto-generated label format
  expectedLabel := fmt.Sprintf("z_campaign_%s", strings.ToLower(strings.ReplaceAll(spec.ID, "_", "-")))
  if !strings.HasPrefix(trimmedLabel, "z_campaign_") {

• Tests (pkg/campaign/validation_test.go): Added TestValidateSpec_TrackerLabelFormat covering prefix validation

• Lock file: Recompiled with correct GH_AW_TRACKER_LABEL: z_campaign_security-alert-burndown

Discovery mechanism in actions/setup/js/campaign_discovery.cjs line 329 already generates campaign labels as z_campaign_${campaignId.toLowerCase().replace(/[_\s]+/g, "-")}, and worker workflows throughout the codebase use this convention.

Original prompt

Campaign orchestrator needs to stop using GH_AW_TRACKER_LABEL: campaign:security-alert-burndown (which yields 0 label-based matches) and instead use the campaign’s actual label convention (z_campaign_security-alert-burndown).

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.