Enable append-only-comments for campaign orchestrators

[Copilot]

Campaign orchestrators were updating the activation comment on each run, losing historical context. Campaign generators already use append-only-comments: true but orchestrators did not.

Changes

• Campaign orchestrator configuration (pkg/campaign/orchestrator.go)

  • Added Messages config with AppendOnlyComments: true to SafeOutputsConfig
  • Positioned after other safe output assignments for consistency

• Test coverage (pkg/campaign/orchestrator_test.go)

  • Added TestBuildOrchestrator_AppendOnlyCommentsEnabled to verify configuration

Behavior

Before: Each campaign run updates the same comment

// Run 1: "Campaign started"
// Run 2: "Campaign in progress" (replaces run 1)
// Run 3: "Campaign complete" (replaces run 2)
// Result: 1 comment with latest state only

After: Each campaign run creates a new comment

// Run 1: "Campaign started"
// Run 2: "Campaign in progress" (new comment)
// Run 3: "Campaign complete" (new comment)
// Result: 3 comments, full audit trail

The JavaScript handler (update_activation_comment.cjs) already supports append-only mode; this change enables it for campaign orchestrators.

Original prompt

Do a ddeep anaylysis of messages safe output and add_comment. It seems that for campaign generation, message updates use the wrong api (update/replace instead of create new comment).

---

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