docs: fix steps: placement in Deterministic Multi-Repo Workflows example

[Copilot]

The "Deterministic Multi-Repo Workflows" code example in the MultiRepoOps docs had steps: incorrectly nested under engine:, causing compilation to fail with Unknown property: steps.

Change

• docs/src/content/docs/patterns/multi-repo-ops.md: Moved steps: from under engine: to a top-level frontmatter key.

# Before (broken)
engine:
  id: claude
  steps:
    - name: Checkout main repo
      ...

# After (correct)
engine:
  id: claude

steps:
  - name: Checkout main repo
    ...

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Docs: MultiRepoOps 'Deterministic Multi-Repo Workflows' example has steps: under engine: which fails compilation</issue_title>
<issue_description>## Page

https://github.github.io/gh-aw/patterns/multi-repo-ops/#deterministic-multi-repo-workflows

Problem

The "Deterministic Multi-Repo Workflows" section shows steps: nested under engine::

engine:
  id: claude
  steps:
    - name: Checkout main repo
      uses: actions/checkout@v5
      ...
    - name: Checkout secondary repo
      uses: actions/checkout@v5
      ...

This does not compile. The compiler rejects steps as an unknown property under /engine:

error: at '/engine' (line 21, column 3): Unknown property: steps

Expected

steps: should be a top-level frontmatter key, not nested under engine::

engine:
  id: claude

steps:
  - name: Checkout main repo
    uses: actions/checkout@v5
    with:
      path: main-repo
  - name: Checkout secondary repo
    uses: actions/checkout@v5
    with:
      repository: org/secondary-repo
      token: ${{ secrets.GH_AW_CROSS_REPO_PAT }}
      path: secondary-repo

Version

gh-aw v0.50.0 (compiler version from lock file)</issue_description>

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

• Fixes Docs: MultiRepoOps 'Deterministic Multi-Repo Workflows' example has steps: under engine: which fails compilation #18090

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[Copilot]

Pull request overview

This PR fixes a critical YAML structure error in the MultiRepoOps documentation where steps: was incorrectly nested under engine:, causing compilation to fail with "Unknown property: steps". The fix correctly moves steps: to be a top-level frontmatter field as specified in the schema.

Changes:

• Corrected YAML structure in the "Deterministic Multi-Repo Workflows" example by moving steps: from under engine: to top-level frontmatter
• Regenerated smoke-copilot.lock.yml workflow file (includes unrelated infrastructure update)

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
docs/src/content/docs/patterns/multi-repo-ops.md	Fixed incorrect YAML structure by moving steps: array from nested under engine: to top-level frontmatter position
.github/workflows/smoke-copilot.lock.yml	Auto-generated lock file with updated compilation output (includes new MCP configuration cleanup step)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This auto-generated lock file includes a new step "Clear MCP configuration for detection" that wasn't present before. Since this file is automatically generated from smoke-copilot.md (which doesn't contain this step definition), this change appears to come from updates to the compilation infrastructure itself.

While this may be expected if the compiler was updated, the PR description doesn't mention this change. If this is an intentional infrastructure update that affects all compiled workflows, it would be helpful to note this in the PR description. If this change is unintentional or if only the documentation fix should be included, consider regenerating the lock file without this additional change.