[instructions] Sync instruction files with release v0.87.5

[github-actions]

Summary

Instructions janitor run for 2026-08-26. Release/change audit: latest release is v0.87.5; no docs/ changes since then needed syncing, and the two .github/aw/*.md changes found in that diff (agent-runtime-instructions.md wording, instructions.md operational-value-designer note) were already current on main. Per the edge-case rule, still ran the size, duplication, and accuracy audits.

Size audit: all 67 .github/aw/*.md files remain under their target limits (largest is 384 lines).

Accuracy audit (against pkg/workflow/safe_outputs_config.go / *_helpers.go / main_workflow_schema.json) found one real bug and several documentation gaps, both fixed:

• Bug: safe-outputs-management.md's push-to-pull-request-branch example documented a non-existent branch: field and a required-title-prefix key (the real yaml tag is title-prefix), and stated cross-repository pushes are "not supported" — the config actually has target-repo, head-repo, head-github-token, base-branch, and allowed-repos for exactly that.
• Gaps: documented previously-missing fields — create-issue/create-pull-request require-temporary-id, add-comment allows-comment-ids, create-discussion min-body-length, create-pull-request close-older-pull-requests/close-older-key/head-repo/head-github-token, update-issue required-labels, merge-pull-request required-title-prefix, close-pull-request allow-body, add-labels issues/pull-requests scoping, dispatch-workflow allowed-refs, github-app ignore-if-missing/permissions, and on.skip-author-associations (syntax-core.md).

Duplication audit found the persona/trigger decision-matrix content repeated across github-agentic-workflows.md, triggers.md, and create-agentic-workflow-trigger-details.md. Rather than risk losing the unique detail each file adds (persona lens vs. intent lens vs. prompt-authoring detail), added short cross-references so triggers.md#decision-matrix is explicitly the canonical source and future trigger-mapping edits are made once.

Files changed (before → after line counts)

File	Before	After
.github/aw/safe-outputs-content.md	287	295
.github/aw/safe-outputs-management.md	306	315
.github/aw/safe-outputs-runtime.md	302	304
.github/aw/safe-outputs-automation.md	303	304
.github/aw/syntax-core.md	166	168
.github/aw/github-agentic-workflows.md	183	185
.github/aw/create-agentic-workflow-trigger-details.md	143	143

All still well under their < 400 (detail files) / < 200 (entry point) targets.

Documentation commits reviewed

None — no commits under docs/ since v0.87.5 (2026-08-25). The two .github/aw/*.md commits found in the release diff were already applied on main.

Test plan

• Reviewed pkg/workflow/safe_outputs_config.go, push_to_pull_request_branch.go, create_pull_request.go, create_issue.go, create_discussion.go, add_comment.go, update_issue.go, merge_pull_request.go, close_entity_helpers.go, add_labels.go, dispatch_workflow.go, safe_outputs_app_config.go, and main_workflow_schema.json to confirm every added/corrected field name and behavior against source.
• No functional code changed; nothing to run beyond doc review.

Generated by 🧹 Instructions Janitor · claude · sonnet50 · 468.3 AIC · ⌖ 21.8 AIC · ⊞ 6.8K · ◷

• expires on Aug 28, 2026, 12:57 AM UTC-08:00

---

Generated by 👨‍🍳 PR Sous Chef · pi · gpt54 · 18.5 AIC · ⌖ 8.2 AIC · ⊞ 6.3K · ◷
_{Comment /souschef to run again}

[github-actions]

✅ Looks great! This PR syncs documentation with the latest code implementation.

Thank you for keeping the instruction files in sync with pkg/workflow/safe_outputs_config.go. The changes cover important accuracy fixes (like the branch: → title-prefix correction in push-to-pull-request-branch) and newly documented fields across safe-outputs and syntax features. The cross-references you added between trigger tables (github-agentic-workflows.md, triggers.md, create-agentic-workflow-trigger-details.md) will help prevent future drift.

This PR is ready for review and merge.

Generated by ✅ Contribution Check · copilot · auto · 51.6 AIC · ⌖ 5.39 AIC · ⊞ 9.3K · ◷

[gh-aw-bot]

gh-aw-pr-sous-chef
@copilot PR Sous Chef triage: this PR still needs a forward-progress pass before maintainer investigation is likely to be productive.

Please do one focused follow-up pass:

• review the current PR state, refresh the branch if needed, and make sure any missing maintainer-facing context is added
• run the pr-finisher skill before handing back for review

Run: https://github.com/github/gh-aw/actions/runs/32957620001

Generated by 👨🍳 PR Sous Chef

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

[Copilot]

gh-aw-pr-sous-chef
@copilot PR Sous Chef triage: this PR still needs a forward-progress pass before maintainer investigation is likely to be productive.
...

Ran a pr-finisher pass: no unresolved review threads exist, the branch is not behind main (base sha d846ab2 matches HEAD~1) and there are no merge conflicts, and make agent-report-progress (fmt/lint/impacted tests) passes cleanly with no changes needed since only .github/aw/*.md files were touched. mergeable_state: blocked reflects pending required status checks/review approval, which requires a maintainer action rather than further code changes. No additional commits were needed this pass.

[gh-aw-bot]

gh-aw-pr-sous-chef
@copilot PR Sous Chef triage: this PR still needs a forward-progress pass before maintainer investigation is likely to be productive.

Please do one focused follow-up pass:

• review the current PR state, refresh the branch if needed, and make sure any missing maintainer-facing context is added
• run the pr-finisher skill before handing back for review

Run: https://github.com/github/gh-aw/actions/runs/32962488926

Generated by 👨‍🍳 PR Sous Chef · pi · gpt54 · 18.5 AIC · ⌖ 8.2 AIC · ⊞ 6.3K · ◷
_{Comment /souschef to run again}

[Copilot]

gh-aw-pr-sous-chef
@copilot PR Sous Chef triage: this PR still needs a forward-progress pass before maintainer investigation is likely to be productive.
...

Re-ran the pr-finisher triage: state is unchanged since the previous pass — no unresolved review threads, no merge conflicts, branch not behind main, and make agent-report-progress passes cleanly with no code changes needed. mergeable_state: blocked is due to the pending gh-aw-bot review request and required status checks, which need a maintainer/reviewer action rather than further agent changes.