[docs] Update glossary - daily scan

[github-actions]

Glossary Updates - 2026-03-10

Scan Type

• Incremental (daily - last 24 hours)
• Full scan (weekly - last 7 days)

Terms Added

• Failure Issue Reporting (report-failure-as-issue:): New safe-outputs option from PR Improve failure issue actionability with generic debug prompt and report-failure-as-issue option #20266 that controls whether workflow run failures are automatically reported as GitHub issues. Defaults to true; set to false to suppress failure issue creation.

Terms Updated

None

Changes Analyzed

• Reviewed 20 commits from the last 24 hours
• Key change: PR Improve failure issue actionability with generic debug prompt and report-failure-as-issue option #20266 introduced report-failure-as-issue: option in safe-outputs

Related Changes

• PR Improve failure issue actionability with generic debug prompt and report-failure-as-issue option #20266: Improve failure issue actionability with generic debug prompt and report-failure-as-issue option
• PR Fix: max-patch-size missing from tools.repo-memory JSON schema #20309: Fix max-patch-size missing from tools.repo-memory JSON schema (already documented in repo-memory reference, no new glossary term needed)

Notes

Other changes were internal refactoring (safe_outputs_generation.go split), bug fixes, and CLI flag additions not requiring glossary updates.

Generated by Glossary Maintainer · ◷

• expires on Mar 12, 2026, 10:19 AM UTC

[Copilot]

Pull request overview

Updates the documentation glossary with a new safe-outputs term describing how to control automatic failure issue creation.

Changes:

• Add a glossary entry for Failure Issue Reporting (report-failure-as-issue:) with a brief description and YAML example.
• Link the new term to the Safe Outputs reference for additional details.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[Copilot]

The default is described as "Defaults to true when safe outputs are configured", but the option itself is simply a boolean with default true (and only applies when safe-outputs is present). Consider rephrasing to match the Safe Outputs reference/schema wording (e.g., "default: true") to avoid implying the default changes based on whether safe outputs are configured.

Suggested change

	A `safe-outputs` option controlling whether workflow run failures are automatically reported as GitHub issues. Defaults to `true` when safe outputs are configured. Set to `false` to suppress failure issue creation for workflows where failures are expected or handled externally:
	A `safe-outputs` option controlling whether workflow run failures are automatically reported as GitHub issues (default: `true`). Set to `false` to suppress failure issue creation for workflows where failures are expected or handled externally: