Update campaign docs: fix discovery/allowed distinction, rename lifecycle page

[Copilot]

Campaign documentation incorrectly conflated discovery-repos/discovery-orgs (search scope) with allowed-repos/allowed-orgs (operation scope). The spec page also lacked required field documentation matching pkg/campaign/validation.go.

Changes

Campaign Spec page (specs.md)

• Clarified field semantics:
  • discovery-*: WHERE to search for worker-created issues/PRs (required when using workflows or tracker-label)
  • allowed-*: WHERE campaign can operate (optional, defaults to current repo)
• Updated example with required KPI fields (baseline, target, time-window-days) and YAML frontmatter delimiters
• Reorganized fields into Required / Required for discovery / Commonly used / Optional sections
• Removed duplicate "Governance (pacing)" heading

Lifecycle page rename

• flow.md → lifecycle.md
• Title: "Campaign Flow & Lifecycle" → "Campaign Lifecycle"
• Updated navigation config and all internal references

Example

Before (incorrect):

# Optional: Repositories this campaign can operate on
allowed-repos:
  - "myorg/service-a"

After (correct):

# Discovery: Where to find worker-created issues/PRs (required with workflows)
discovery-repos:
  - "myorg/service-a"

# Optional: Restrict where campaign can operate (defaults to current repo)
# allowed-repos:
#   - "myorg/service-a"

Original prompt

Update campaign docs according to actual implementation. Make sure the Campaign Spec page is up to date and rename the "Flow & lifecycle" page to just Campaign lifecycle (draw inspiration from https://github.com/githubnext/gh-aw/blob/481f56df77fe841a905448f829618b5c501db6fe/docs/src/content/docs/guides/campaigns/architecture.md)

---

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