[docs] Update glossary - daily scan

[github-actions]

Glossary Updates - 2026-02-04

Scan Type

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

Terms Added

Operational Patterns Section (8 new terms):

• DispatchOps: Manual workflow execution via the GitHub Actions UI or CLI using the workflow_dispatch trigger. Perfect for on-demand tasks, testing, and workflows requiring human judgment about timing.

• IssueOps: Automated issue management that analyzes, categorizes, and responds to issues when they are created. Uses safe outputs for secure triage without write permissions.

• LabelOps: Workflows triggered by label changes on issues and pull requests. Uses labels as workflow triggers, metadata, and state markers.

• MemoryOps: Stateful workflows that persist data between runs using cache-memory and repo-memory. Enables progress tracking, resumption after interruptions, and data sharing.

• MultiRepoOps: Cross-repository coordination that extends automation patterns across multiple GitHub repositories using secure authentication and cross-repository safe outputs.

• ProjectOps: AI-powered GitHub Projects board management that automates issue triage, routing, and field updates (relocated from Advanced Features section).

• SideRepoOps: Development pattern where workflows run from a separate "side" repository that targets your main codebase for cleaner separation.

• SpecOps: Maintaining and propagating W3C-style specifications using the w3c-specification-writer agent with RFC 2119 keywords.

• TrialOps: Testing and validation pattern that executes workflows in isolated trial repositories before production deployment.

Terms Updated

• ProjectOps: Relocated from "Advanced Features" section to new "Operational Patterns" section for better organization alongside other operational patterns.

Changes Analyzed

Reviewed commit from the last 24 hours:

• 77f96d7: chore: improve orchestration and projects instructions (chore: improve orchestration and projects instructions #13666)

The recent commit improved orchestration and projects documentation. During analysis, I discovered that multiple operational patterns (with the "-Ops" suffix) were documented throughout the guides and examples but not represented in the glossary. These patterns represent important workflow architectures that users need to understand.

Structure Improvements

• Added new section: "Operational Patterns" to group all -Ops workflow patterns together
• Improved organization: Moved ProjectOps from "Advanced Features" to "Operational Patterns" for consistency
• Enhanced discoverability: All operational patterns now have concise definitions with links to detailed guides

Notes

All operational patterns follow a consistent format:

• Brief definition
• Use for: section with common use cases
• Link to detailed guide or example

This structure provides users with:

1. Quick understanding of what each pattern does
2. Guidance on when to use each pattern
3. Easy navigation to in-depth documentation

---

This daily scan ensures the glossary stays synchronized with the evolving documentation and helps users discover available workflow patterns.

AI generated by Glossary Maintainer

• expires on Feb 6, 2026, 10:22 AM UTC