Fix: Scope Campaign Validation to Specific Files When Compiling

Summary

Fixed an issue where campaign validation was running on all campaigns regardless of which workflows were being compiled. The validation is now properly scoped:

• When compiling specific non-campaign workflows → no campaign validation
• When compiling specific campaign files → validates only those campaigns
• When compiling all workflows → validates all campaigns

Changes Made

• Modified compileSpecificFiles to track which specific campaign files are being compiled (list of paths instead of boolean)
• Updated runPostProcessing to accept list of campaign files
• Enhanced validateCampaigns to filter validation to specific campaign files when provided
• Campaign validation now properly scoped based on compilation context:
  • Compiling all workflows in a directory → validates ALL campaigns
  • Compiling specific campaign files → validates ONLY those campaigns
  • Compiling non-campaign workflows → skips campaign validation entirely

Verification

✅ Non-campaign workflows skip campaign validation:

$ ./gh-aw compile smoke-copilot
✓ Compiled 1 workflow(s): 0 error(s), 0 warning(s)

✅ Specific campaign files validate only that campaign:

# Before: validated all 7 campaigns
$ ./gh-aw compile my-workflow.campaign.md
⚠ Campaign validation: found 7 problem(s) in campaign specs

# After: validates only the 1 campaign being compiled
$ ./gh-aw compile docs-quality-maintenance-project67.campaign.md
ℹ Validating 1 campaign spec(s)...
⚠ Campaign validation: found 6 problem(s) in campaign specs

✅ All workflows still validates all campaigns:

$ ./gh-aw compile
⚠ Campaign validation: found 7 problem(s) in campaign specs
⚠ Compiled 127 workflow(s)

Files Modified

• pkg/cli/compile_orchestration.go - Track campaign files list and pass to post-processing
• pkg/cli/compile_post_processing.go - Accept campaign files list parameter
• pkg/cli/compile_campaign.go - Filter validation to specific campaign files when provided

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.