[docs] docs: reduce bloat in IssueOps guide

[github-actions]

Summary

Cleaned up the IssueOps documentation by removing bloat and consolidating verbose content while preserving all essential information.

Changes Made

Safe Output Architecture Section

• Before: 5-item bullet list explaining security benefits
• After: Single concise paragraph with the same information

Accessing Issue Context Section

• Before: 4-item bullet list describing sanitization features
• After: Compact prose integrating all security features in parentheses

Automated Bug Report Triage Example

• Before: Verbose instructions with 12 bullet points across two separate lists
• After: Compact 4-item bullet list using arrow notation (→) for clarity

Metrics

• Lines: 110 → 91 (17% reduction)
• Bullet points: 20 → 8 (60% reduction)
• Content preserved: 100% (all essential information maintained)

Screenshot

The cleaned documentation page rendered in Astro Starlight:

Blocked Domains

No blocked domains encountered during screenshot capture - all CSS, fonts, and resources loaded successfully.

---

File cleaned: docs/src/content/docs/guides/issueops.md

This file was selected from the pool of uncleaned documentation files as it had the highest bullet point count (20), indicating significant list bloat.

AI generated by Documentation Unbloat

[Copilot]

Pull Request Overview

This PR streamlines the IssueOps documentation by condensing verbose bullet lists into concise prose while maintaining all essential information. The changes reduce overall length by 17% and bullet points by 60%.

Key Changes:

• Converted the Safe Output Architecture security benefits from a 5-item list into a single integrated sentence
• Consolidated the Accessing Issue Context sanitization features from a 4-item list into an inline parenthetical
• Compressed the Bug Report Triage example from 12 bullets into 4 arrow-notation items

---

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

[Copilot]

[nitpick] This sentence has become a run-on with multiple clauses. Consider breaking it into two sentences for better readability: 'IssueOps workflows use the add-comment safe output to ensure secure comment creation with minimal permissions. The main job runs with contents: read while comment creation happens in a separate job with issues: write permissions, automatically sanitizing AI content and preventing spam.'

Suggested change

	IssueOps workflows use the `add-comment` safe output to ensure secure comment creation with minimal permissions. The main job runs with `contents: read` while comment creation happens in a separate job with `issues: write` permissions, automatically sanitizing AI content and preventing spam:
	IssueOps workflows use the `add-comment` safe output to ensure secure comment creation with minimal permissions. The main job runs with `contents: read`, while comment creation happens in a separate job with `issues: write` permissions. This architecture automatically sanitizes AI content and prevents spam:

[Copilot]

[nitpick] The parenthetical list of security features is awkwardly structured. Consider rephrasing to: 'IssueOps workflows access sanitized issue content through the needs.activation.outputs.text variable, which combines the issue title and description while removing security risks (neutralizes @mentions, filters URIs, and protects against injection).'

Suggested change

	IssueOps workflows access sanitized issue content through the `needs.activation.outputs.text` variable, which combines the issue title and description while removing security risks (@mention neutralization, URI filtering, injection protection):
	IssueOps workflows access sanitized issue content through the `needs.activation.outputs.text` variable, which combines the issue title and description while removing security risks (neutralizes @mentions, filters URIs, and protects against injection):

[github-actions]

Agentic Changeset Generator triggered by this pull request.