[docs] Remove bloat from glossary

[github-actions]

Summary

Reduced verbosity in the glossary documentation while preserving all essential information.

Changes Made

• 39% reduction: 488 → 298 lines (190 lines removed)
• Consolidated excessive bullet points into concise prose
• Removed repetitive "Use for:" sections from all operational patterns
• Eliminated redundant code examples
• Streamlined verbose definitions without losing technical accuracy
• Maintained all essential information, links, and technical details

Key Improvements

Core Concepts: Condensed verbose explanations while keeping all key information. For example, "Agentic" definition reduced from 8 lines to 3 lines without losing meaning.

Operational Patterns: Removed repetitive "Use for:" bullet lists from all 13 operational patterns (ChatOps, DailyOps, DataOps, etc.). Each pattern now has a concise 1-2 sentence description with a link to detailed documentation.

Tools and Integration: Streamlined definitions for MCP, Safe Inputs, Safe Outputs, and other technical terms. Removed redundant code examples that duplicated information from reference documentation.

GitHub Terms: Condensed verbose explanations of GitHub Actions, Projects, secrets, and other infrastructure terms.

Screenshot Issue

⚠️ Unable to capture screenshots due to network isolation between Playwright Docker container and the local preview server (server listening on 127.0.0.1:4321 is not accessible from containerized Playwright).

Impact

This change improves documentation readability by:

• Reducing scrolling and cognitive load
• Making definitions easier to scan
• Maintaining professional, concise technical writing style
• Preserving all essential information for users

References:

• §21991728458

AI generated by Documentation Unbloat

• expires on Feb 15, 2026, 3:17 PM UTC

[Copilot]

Pull request overview

This PR streamlines the glossary reference page to improve scanability and reduce repetition while keeping the same set of terms and outward links for deeper documentation.

Changes:

• Condenses many glossary entries from multi-bullet explanations into 1–2 sentence definitions.
• Removes repetitive “Use for:” sections across Operational Patterns.
• Drops redundant inline code examples that duplicated reference documentation.

Comments suppressed due to low confidence (1)

docs/src/content/docs/reference/glossary.md:50

• Use "Markdown" (capital M) when referring to the file/format ("workflow Markdown file" and "referencing the Markdown for instructions") to keep terminology consistent with other entries (e.g., "Markdown workflows").

The compiled GitHub Actions workflow file from a workflow markdown file (`.md`). Contains complete GitHub Actions YAML with security hardening applied. Both `.md` and `.lock.yml` files should be committed to version control. At runtime, GitHub Actions executes the lock file using a coding agent while referencing the markdown for instructions.

---

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

[Copilot]

Consider restoring the internal link for "agentic workflow" (e.g., linking it to the "Agentic Workflow" section) so readers can jump directly to the term. This keeps navigation consistent with the page’s note that terms link to their definitions.

Suggested change

	The AI system that powers the agentic workflow - essentially "which AI to use" to execute workflow instructions. GitHub Agentic Workflows supports multiple engines, with GitHub Copilot as the default.
	The AI system that powers the [agentic workflow](#agentic-workflow) - essentially "which AI to use" to execute workflow instructions. GitHub Agentic Workflows supports multiple engines, with GitHub Copilot as the default.

[Copilot]

Use the proper noun capitalization "Markdown" here for consistency with the rest of the doc and to avoid reading as a generic adjective (e.g., "Written in Markdown instead of complex YAML").

This issue also appears on line 50 of the same file.

Suggested change

An AI-powered workflow that reasons, makes decisions, and takes autonomous actions using natural language instructions. Written in markdown instead of complex YAML, agentic workflows interpret context and adapt behavior flexibly. For example, instead of "if issue has label X, do Y", you write "analyze this issue and provide helpful context", and the AI decides what's helpful based on the specific issue content.

An AI-powered workflow that reasons, makes decisions, and takes autonomous actions using natural language instructions. Written in Markdown instead of complex YAML, agentic workflows interpret context and adapt behavior flexibly. For example, instead of "if issue has label X, do Y", you write "analyze this issue and provide helpful context", and the AI decides what's helpful based on the specific issue content.