[instructions] Sync instruction files with release v0.82.9

[github-actions]

Summary

Syncs .github/aw instruction files with release v0.82.9. All changes are documentation/reference corrections — no workflow logic changed.

Changes by file

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

• create-code-scanning-alert.max: corrects documented default from unlimited to 40
• missing-tool.create-issue: clarifies default is false when the block is explicitly set; remains true only when the block is omitted entirely
• missing-tool: adds new report-as-failure field (default: true) to classify the run as an agent failure
• missing-data.create-issue: same default-behaviour clarification as missing-tool
• missing-data: adds new report-as-failure field (default: true)

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

• create_issue body maximum length: corrects value from 65536 to 65000 characters

.github/aw/syntax-core.md

• skip-roles: adds triage role and maintain as an alias for maintainer to the available-roles list

.github/aw/syntax-tools-imports.md

• timeout: unifies documented default to 60 s for all engines (previously stated Claude: 60 s, Codex: 120 s)

.github/aw/workflow-patterns.md

• Condenses the single-job constraint bullet list into a single sentence with a cross-reference to workflow-constraints.md

Impact

• Behaviour change (runtime): none — instruction files only
• Consumers affected: authors reading .github/aw/ docs will see corrected defaults and two new report-as-failure options for missing-tool / missing-data safe outputs
• Breaking changes: none

Generated by PR Description Updater for #45422 · 31.8 AIC · ⌖ 5.49 AIC · ⊞ 4.7K · ◷

[github-actions]

Hey @github-actions 👋 — thanks for this surgical janitor pass syncing the instruction files with release v0.82.9! The accuracy fixes (especially the create_issue body max, the missing-tool/missing-data create-issue defaults, and the tool timeout correction) are well-sourced and the PR description traces each change back to the Go source of truth.

One small flag:

• No test changes — this is a documentation-only PR, so the absence of test file changes is expected and not a real concern. The checklist mechanically flags it, but it doesn't apply here.

Overall this looks clean and ready for review. If the team wants to add a validation test that spot-checks a known constant against the instruction file text, here's a prompt:

Add a test (or extend an existing one) that reads the `MaxBodyLength` constant from `safe_outputs_validation_config.go` and asserts it matches the value documented in `.github/aw/safe-outputs-content.md`. This would catch future drift between code and instruction files automatically.

Generated by ✅ Contribution Check · 112.9 AIC · ⌖ 10.7 AIC · ⊞ 6.2K · ◷