update docs

Author: mnkiefer

docs/src/content/docs/guides/campaigns.md

@@ -272,13 +272,33 @@ gh aw campaign status --json       # JSON status output
 gh aw campaign new security-q1-2025         # Scaffold a new campaign spec
 gh aw campaign validate                     # Validate all campaign specs
 gh aw campaign validate --json              # JSON validation report
-gh aw campaign validate --no-strict         # Report problems without failing
+gh aw campaign validate --strict=false      # Report problems without failing
 ```
 
 This gives you a centralized, Git-backed catalog of campaigns in the
 repository, aligned with the executable workflows in `.github/workflows/` and
 the data they write into repo-memory.
 
+### Compile Integration and Orchestrators
+
+Campaign spec files participate in the normal `compile` workflow:
+
+- `gh aw compile` automatically validates all `.github/workflows/*.campaign.md` specs before compiling workflows.
+- Validation checks both the spec itself (IDs, tracker labels, lifecycle state, etc.) and that all referenced `workflows` exist in `.github/workflows/`.
+- If any campaign spec has problems, `compile` fails with a `campaign validation failed` error until issues are fixed.
+
+For experimentation, you can also enable an **orchestrator workflow** per campaign:
+
+```bash wrap
+GH_AW_EXPERIMENTAL_CAMPAIGN_ORCHESTRATOR=1 gh aw compile
+```
+
+When this environment variable is set and specs are valid:
+
+- Each `<name>.campaign.md` generates an orchestrator markdown workflow named `<name>-campaign.md` next to the spec.
+- The orchestrator is compiled like any other workflow to `<name>-campaign.lock.yml`.
+- This makes campaigns first-class, compilable entry points while keeping specs declarative.
+
 ### Interactive Campaign Designer
 
 For a more guided, conversational experience, this repo also includes a

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

@@ -155,6 +155,8 @@ gh aw compile --strict --zizmor        # Strict mode with security scanning
 gh aw compile --validate --strict      # Validate schema and enforce strict mode
 ```
 
+**Campaign specs and orchestrators:** In repositories that define campaign spec files under `.github/workflows/*.campaign.md`, `gh aw compile` first validates those specs (including referenced `workflows`) and fails the compilation if any problems are found. When the environment variable `GH_AW_EXPERIMENTAL_CAMPAIGN_ORCHESTRATOR=1` is set, `compile` also synthesizes an orchestrator workflow for each valid spec (for example, `security-compliance.campaign.md` → `security-compliance-campaign.md`) and compiles it to a corresponding `.lock.yml` file.
+
 See [Strict Mode reference](/gh-aw/reference/frontmatter/#strict-mode-strict) for frontmatter configuration and [Security Guide](/gh-aw/guides/security/#strict-mode-validation) for best practices.
 
 ### Testing