docs: make Stage context explicit in promotion step examples

[MuhanedYahya]

Issue Reference

Closes #6275

Description

Several promotion step reference examples used ${{ outputs.alias.field }}
without any surrounding YAML context. This created an unstated assumption
that the reader understood the snippet to be inside a Stage's
spec.promotionTemplate — not inside a (Cluster)PromotionTask, where
the correct syntax is ${{ task.outputs['alias'].field }}.

As noted in the original review on #6273, the fix is to make the context
explicit in each affected example rather than leaving it as an assumption.

Checklist

• The PR is linked to an existing issue.
• The linked issue has no blocking labels (kind/proposal,
  needs discussion, needs research, maintainer only, area/security,
  size/large, size/x-large, size/xx-large).
• I have added or updated tests as appropriate.
• I have added or updated documentation as appropriate.

AI Use Disclosure

Select one:

• This PR was written by a human without AI assistance.
• This PR was written by a human with AI assistance. A human has reviewed every line prior to opening the PR.
• This PR was written by an AI with human supervision. A human has reviewed every line prior to opening the PR.
• This PR was written entirely by AI. No human has reviewed this prior to opening the PR.

Sign-Off

• All commits are signed off (git commit -s) (required)
• All commits are cryptographically signed (git commit -S) (encouraged)

[netlify]

✅ Deploy Preview for docs-kargo-io ready!

Name	Link
🔨 Latest commit	37037b9
🔍 Latest deploy log	https://app.netlify.com/projects/docs-kargo-io/deploys/6a42e566d41e67000840118b
😎 Deploy Preview	https://deploy-preview-6277.docs.kargo.io
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[MuhanedYahya]

@krancour any updates? i see a conflict in docs which wasn't there when i first forked the repo

[EronWright]

Summary of changes — consolidation of #6275 work

For context on how this PR evolved: there were two PRs addressing #6275 from slightly different angles:

• This PR (docs: make Stage context explicit in promotion step examples #6277, @MuhanedYahya) — makes the full Stage context explicit in the example YAML, so it's clear the examples live in a Stage's spec.promotionTemplate.
• docs: clarify promotion output context #6284 (@AndresGuido9820) — added an inline # Or task.outputs in a (Cluster)PromotionTask pointer at each previous-step output reference.

Since both edit the same example files, they couldn't both land. So both approaches have been consolidated here:

• Every output-referencing example now shows the explicit Stage context and carries the inline # Or task.outputs in a (Cluster)PromotionTask pointer.
• The pointer was extended across all the reference pages identified in the discussion: gha-wait-for-workflow, git-commit, jfrog-evidence, jira, oci-push, and send-message.
• For the message: | block-scalar case in git-commit, the comment sits on the | indicator line so it isn't absorbed into the literal commit message.
• Pages whose examples are already framed as (Cluster)PromotionTask (compose-output, snow-*, tf-plan) already use task.outputs correctly and were left untouched.

@AndresGuido9820's contribution is preserved via a Co-authored-by trailer, and #6284 has been closed in favor of this PR.

Status: rebased clean (MERGEABLE), CI green. Ready for review @krancour.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 58.63%. Comparing base (45616df) to head (37037b9).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6277      +/-   ##
==========================================
- Coverage   58.63%   58.63%   -0.01%     
==========================================
  Files         505      505              
  Lines       42691    42691              
==========================================
- Hits        25033    25031       -2     
- Misses      16124    16125       +1     
- Partials     1534     1535       +1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[hairyhum]

LGTM