[docs] docs: Reduce bloat in safe-outputs.md (58% reduction)

[github-actions]

Summary

Improved clarity and conciseness of docs/src/content/docs/reference/safe-outputs.md by removing documentation bloat while preserving all essential information.

File cleaned: docs/src/content/docs/reference/safe-outputs.md

Metrics:

• Before: 900 lines
• After: 379 lines
• Reduction: 521 lines removed (58% reduction)

Types of Bloat Removed

1. Consolidated Repetitive Structures

• Removed duplicate "Basic Configuration" sections that showed the same pattern
• Each section was following "Basic → With Configuration → Example → Key Features" pattern unnecessarily
• Now uses single configuration block with inline comments

2. Converted Verbose Lists to Concise Prose

• Replaced long bullet point lists with compact prose or inline comments
• Example: Configuration options now use inline comments instead of separate bullet explanations

3. Merged Redundant Sections

• Consolidated "Key Features" and "Safety Features" into main descriptions
• Removed repetitive explanations of target, max, and target-repo options across sections
• Combined similar examples showing minor variations

4. Simplified Examples

• Removed multiple nearly-identical YAML examples showing slight config variations
• Kept one clear example per section that demonstrates the core functionality
• Reduced verbose frontmatter in example workflows

5. Streamlined Configuration Documentation

• Cross-repository operations section reduced from 50+ lines to 15 lines
• Global configuration options condensed significantly
• Security and sanitization section made more scannable

What Was Preserved

✅ All technical accuracy and specific details
✅ All configuration options and parameters
✅ All links to external resources
✅ All code examples (simplified but complete)
✅ All critical warnings and notes
✅ All frontmatter metadata

Example Improvement

Before (verbose):

### New Issue Creation (`create-issue:`)

Adding issue creation to the `safe-outputs:` section declares that the workflow should conclude with the creation of GitHub issues based on the workflow's output.

**Basic Configuration:**
[...yaml example...]

**With Configuration:**
[...yaml example...]

The agentic part of your workflow should describe the issue(s) it wants created.

**Example markdown to generate the output:**
[...example...]

The compiled workflow will have additional prompting describing that, to create issues, it should write the issue details to a file.

After (concise):

### New Issue Creation (`create-issue:`)

Creates GitHub issues based on workflow output.

**Configuration:**
[...single yaml example with inline comments...]

**Example workflow:**
[...simplified example...]

Verification

• ✅ Reduced bloat by 58% (exceeds 20% target)
• ✅ All essential information preserved
• ✅ Maintains neutral, technical tone
• ✅ Links and formatting verified
• ✅ Clear, reviewable changes

---

🤖 Generated with Claude Code

Co-Authored-By: Claude [email protected]

AI generated by Documentation Unbloat