Fix invalid YAML example in Job Outputs docs

[Copilot]

The Job Outputs reference example mixed a workflow YAML block with markdown prompt text in the same fenced code block, which produced invalid YAML and misrepresented how workflow files are structured.

• Corrected the example by separating the workflow YAML from the prompt body into distinct fenced blocks.
• Kept the YAML example limited to the jobs definition and job outputs.
• Added a dedicated markdown example for the prompt text that references ${{ needs.release.outputs.version }}.

jobs:
  release:
    outputs:
      release_id: ${{ steps.get_release.outputs.release_id }}
      version: ${{ steps.get_release.outputs.version }}
    steps:
      - id: get_release
        run: echo "version=${{ github.event.release.tag_name }}" >> $GITHUB_OUTPUT

Generate highlights for release ${{ needs.release.outputs.version }}.

• Fixes [deep-report] Fix invalid YAML in Job Outputs example (docs/reference/steps-jobs.md) #56943

[Copilot]

🟢 Approval recommended

The focused documentation change produces valid, clearly separated examples.

Pull request overview

Separates the Job Outputs YAML configuration from its markdown prompt, fixing the invalid mixed-language example.

Changes:

• Closes the YAML fence before the prompt.
• Adds a dedicated markdown fence for prompt text.

File summaries

File	Description
docs/src/content/docs/reference/steps-jobs.md	Corrects Job Outputs example formatting.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Balanced

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

🎉 This pull request is included in a new release.

Release: v0.87.10