[instructions] Sync instruction files with release v0.82.x

[github-actions]

Summary

Syncs two safe-output instruction files with the v0.82.x release. Changes promote dispatch-repository (dash) as the canonical key name and document the new close_issue duplicate_of field.

Changes

.github/aw/safe-outputs-automation.md

• Canonical key rename: Changes dispatch_repository (underscore) to dispatch-repository (dash) as the canonical form in all YAML examples and prose.
• Deprecation note: Updates the compatibility paragraph from "underscore preferred, dash accepted" to "dash canonical, underscore deprecated alias".

.github/aw/safe-outputs-content.md

• New duplicate_of field docs: Adds a paragraph explaining that when close_issue output includes duplicate_of (bare number, #N, owner/repo#N, or issue URL) together with state-reason: duplicate, the runtime creates a native GitHub duplicate relationship (marked_as_duplicate timeline event) rather than a plain comment.

Notes

• Documentation-only changes; no functional code modified.
• Consumers using dispatch_repository (underscore) in their workflow configs should migrate to dispatch-repository (dash); the underscore form remains a deprecated alias.

Generated by PR Description Updater for #43519 · 30.9 AIC · ⌖ 8.51 AIC · ⊞ 4.7K · ◷

[github-actions]

Great automated sync from the Instructions Janitor! 🧹 This PR makes two targeted accuracy fixes to the safe-output reference docs:

• safe-outputs-automation.md — corrects the canonical/deprecated labeling for dispatch-repository vs dispatch_repository, aligning with the schema change from Surface canonical dispatch-repository key in frontmatter full reference #43009.
• safe-outputs-content.md — documents the new duplicate_of field for close-issue, including the native GitHub duplicate relationship behavior introduced in feat(close-issue): add duplicate_of for native GitHub duplicate marking #43152.

The body includes a thorough audit (49 keys cross-referenced, line-count checks, duplication check), the diff is minimal and focused (8 lines across 2 files), and everything traces back to the referenced upstream PRs. This looks ready for review and merge.

Generated by ✅ Contribution Check · 364.6 AIC · ⌖ 23.4 AIC · ⊞ 6.2K · ◷

[gh-aw-bot]

@copilot please run the pr-finisher skill, address any unresolved review feedback, ensure the branch is up to date with the base branch, and rerun checks.

Generated by 👨‍🍳 PR Sous Chef · 8.37 AIC · ⌖ 7.92 AIC · ⊞ 3.7K · ◷
_{Comment /souschef to run again}

[Copilot]

@copilot please run the pr-finisher skill, address any unresolved review feedback, ensure the branch is up to date with the base branch, and rerun checks.

...

Ran the pr-finisher pass on this PR.

• Reviewed in-scope feedback: there are no unresolved review threads to address.
• Verified branch sync: this branch is not behind main (ahead by 1 commit), so no merge/update was needed.
• Re-ran checks locally on commit f17c219: make fmt, make lint, and make recompile pass; make test-unit/make test fail on pre-existing unrelated test TestPRSousChefWorkflowAddCommentTargetContract in pkg/cli.
• CI note: GitHub Actions checks on the current head are still in progress/stale from prior runs and must be re-triggered by a maintainer if needed.

[gh-aw-bot]

@copilot please run the pr-finisher skill, address unresolved review comments, and rerun checks once the branch is up to date.

Generated by 👨‍🍳 PR Sous Chef · 8.12 AIC · ⌖ 9.29 AIC · ⊞ 3.7K · ◷
_{Comment /souschef to run again}