Drop passive campaigns and make workflow execution default

[Copilot]

Campaigns previously had two modes: "passive" (ProjectOps pattern) and "active" (workflow execution with execute-workflows: true). This created unnecessary complexity since there's no legacy to support. All campaigns now execute workflows by default.

Changes

Core model simplification:

• Removed ExecuteWorkflows boolean field from CampaignSpec struct
• Orchestrator always includes workflow execution instructions when workflows are configured
• Removed execute-workflows field from JSON schema

Documentation cleanup:

• Removed "Campaign modes" section and ProjectOps pattern references
• Eliminated migration guides between modes
• Updated getting-started, technical-overview, specs, and glossary
• Simplified campaign creation prompts

Example before:

workflows:
  - framework-scanner
  - framework-upgrader
execute-workflows: true  # Required flag

Example after:

workflows:
  - framework-scanner
  - framework-upgrader
# Workflows execute by default when configured

The orchestrator now executes listed workflows sequentially, creates missing workflows if needed, and uses outputs to coordinate campaign progress—no flag required.

Original prompt

Drop passive campaigns, there is no legacy and make active campaigns just "campaigns". Make sure the code is fully functional and drop option: active since this will be the default.

---

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