[Copilot]

The compile --purge flag was not removing orphaned .campaign.g.md files or their corresponding .campaign.lock.yml files when the source .campaign.md file was deleted.

Changes

• Modified purgeOrphanedCampaignOrchestrators() in pkg/cli/compile_batch_operations.go:

  • Changed from no-op to actively purging orphaned .campaign.g.md files
  • Scans for .campaign.g.md files without corresponding .campaign.md sources
  • Deletes orphaned files with success/failure messages

• Updated test expectations in pkg/cli/compile_command_test.go:

  • TestCompileWorkflows_PurgeCampaignOrchestrators now expects orphaned .campaign.g.md files to be deleted
  • Maintains verification that valid files with sources remain untouched

Behavior

Campaign file lifecycle:

.campaign.md → .campaign.g.md → .campaign.lock.yml

When source is deleted:

$ rm .github/workflows/test.campaign.md
$ gh aw compile --purge
✓ Removed orphaned campaign orchestrator file: test.campaign.g.md
✓ Removed orphaned campaign orchestrator lock file: test.campaign.lock.yml

Files with valid sources remain intact. The existing purgeOrphanedCampaignOrchestratorLockFiles() already handled .campaign.lock.yml files correctly.

Original prompt

The 'compile --purge' purging mode should delete orphaned .campaign.g.md files, and their related .lock.yml files.

---

💡 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.

[pelikhan]

@copilot format, lint