Move campaign command documentation to dedicated Campaigns section

[Copilot]

Documentation Reorganization Complete ✓

• Understand the issue: campaign command is misplaced under compile section
• Verify campaign command group assignment (analysis group in main.go:543)
• Locate current documentation placement (lines 270-294 under Building section)
• Identify correct section (Monitoring section, lines 360-403)
• Move campaign command documentation from Building to Monitoring section
• Update campaign specs reference in compile section to be a brief note with cross-reference
• Move campaign to its own dedicated section per feedback
• Merge main branch and recompile workflows
• Verify documentation structure matches command groups

Changes Summary

Final Structure

### Monitoring
  ├── status
  ├── logs
  └── audit

### Campaigns  ← New dedicated section
  └── campaign

### Management
  ├── enable
  ├── disable
  └── ...

What Changed

1. Created new "Campaigns" section (###) for campaign command
2. Positioned between Monitoring and Management sections
3. Merged main branch and resolved conflicts
4. Recompiled all 117 workflows successfully

Previous Changes

• Moved campaign from Building section
• Updated compile section with brief campaign specs note + cross-reference
• Added anchor link for easy navigation

Verification

• ✓ Command group: "analysis" (main.go:543)
• ✓ Own dedicated section: "Campaigns"
• ✓ Positioned logically between Monitoring and Management
• ✓ Anchor link format: consistent with existing links
• ✓ Main branch merged
• ✓ All workflows recompiled

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[cli-consistency] Campaign command documentation misplaced under compile section</issue_title>
<issue_description>## Issue Description

Type: Documentation clarity issue
Priority: Low

Current State

The documentation for the campaign command section appears within the compile command section, which may confuse users who are looking for information about campaign management.

Evidence from Documentation

From docs/src/content/docs/setup/cli.md:

Lines 271-294: The "Campaign specs and orchestrators" section and the campaign command documentation appear as subsections under the compile command section (which starts at line 240).

Lines 276-294: The campaign command is documented with all its subcommands and examples, but it's embedded within compile command documentation.

Issue

The campaign command is actually a standalone top-level command (confirmed in main.go line 514), not a subcommand of compile. The current documentation structure incorrectly suggests it's related to or part of the compile command.

From the command group tests, campaign should be in the "Analysis Commands" group, not nested under the "Development Commands" (where compile lives).

Actual Impact

Users may:

1. Miss the campaign command when looking for analysis tools
2. Think campaign is somehow a subcommand or feature of compile
3. Not find campaign documentation when searching for "Analysis Commands"

Expected Behavior

The campaign command should have its own standalone section under the "Analysis Commands" heading in the documentation, similar to how logs and audit commands are documented.

Suggested Fix

1. Move the campaign documentation (lines 276-294) from the compile section
2. Create a new section in the "Monitoring" or "Analysis" section
3. Keep only the campaign-spec-related compilation behavior documentation in the compile section (lines 271-274)
4. Add a cross-reference in the compile section pointing to the full campaign command documentation

Example structure:

### Building

#### `compile`
[...existing content...]

Campaign specs and orchestrators: When campaign specs exist, compile validates them. See the [`campaign` command](#campaign) for management.

[...]

### Analysis (or Monitoring)

#### `campaign`
Inspect and validate first-class campaign definitions...
[full campaign documentation here]

AI generated by CLI Consistency Checker

Comments on the Issue (you are @copilot in this section)

• Fixes [cli-consistency] Campaign command documentation misplaced under compile section #6961

---

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

[pelikhan]

@copilot move campaign to own section

[Copilot]

@copilot move campaign to own section

Done in 6e0e6fe. Campaign command now has its own dedicated "Campaigns" section positioned between Monitoring and Management.

Structure:

### Monitoring
  ├── status
  ├── logs
  └── audit

### Campaigns  ← New section
  └── campaign

### Management
  └── ...

[pelikhan]

@copilot merge main and recompile

[Copilot]

@copilot merge main and recompile

Done in 39944ea. Merged origin/main and recompiled all 117 workflows successfully.

Merge details:

• Resolved conflicts in lock files by accepting our version
• Rebuilt binary with latest changes
• Recompiled all workflows
• All 117 workflows compiled successfully (45.7 MB total)