Fix orchestrator to monitor workers via tracker-id instead of workflow runs

[Copilot]

Campaign orchestrators were monitoring workers by querying workflow runs API and parsing artifacts, which is brittle and complex. Workers already embed tracker-ids in created issues as HTML comments for this exact purpose.

Changes

• pkg/campaign/prompts/orchestrator_instructions.md: Changed monitoring strategy from workflow runs API to issue search by tracker-id

  • Removed: github-list_workflow_runs + artifact parsing
  • Added: github-search_issues with query "<!-- tracker-id: WORKER_ID -->" in:body

• pkg/campaign/orchestrator_test.go: Added TestBuildOrchestrator_TrackerIDMonitoring to verify:

  • Orchestrator includes tracker-id search instructions
  • No references to .lock.yml files or list_workflow_runs

• Generated orchestrators: Recompiled go-file-size-reduction.campaign.g.md and variants with updated instructions

Example

Workers create issues with embedded tracker-id:

## Issue Title

Content here...

<!-- tracker-id: daily-file-diet -->

Orchestrator discovers them:

repo:githubnext/gh-aw "<!-- tracker-id: daily-file-diet -->" in:body

This aligns with the tracker-id design pattern documented in the glossary and removes the workflow file name dependency.

Original prompt

Fix orchestrator in Go file size reduction campaign to not monitoring the daily file diet issues.
The orchestrator should monitor worker workflow runs (via tracker-id), discover issues created by workers, and add them to project board, update board status, and report on campaign progress.

Custom agent used: debug-agentic-workflow
Debug and refine agentic workflows using gh-aw CLI tools - analyze logs, audit runs, and improve workflow performance

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.