# Label Taxonomy

This document catalogs the issue labels used for MCP workflows, including Jenkins and GlitchTip (observability).

> **Approval Required:** Do not create or apply new labels in `manage_labels.py` without explicit owner approval of this document.

## Existing Labels

* **`jenkins`**
  * Description: Jenkins integration
  * Color: `d93f0b`
  * Use: Used to mark issues, PRs, or tasks that involve the `jenkins-mcp` boundaries, CI/CD designs, or build failures.

* **`glitchtip`**
  * Description: GlitchTip integration
  * Color: `b60205`
  * Use: Used to mark issues related to the `glitchtip-mcp` boundary and observability integration.

## Proposed / Missing Labels

* **`observability`**
  * Proposed Description: Observability, metrics, and monitoring tasks
  * Proposed Color: `5319e7`
  * Use: Broader than GlitchTip alone; covers logging, metrics, traces, and general observability pipeline improvements.

* **`source:glitchtip`**
  * Proposed Description: Issue filed automatically by GlitchTip orchestration
  * Proposed Color: `b60205`
  * Use: Applied automatically by the orchestrator when a GlitchTip error event is converted into a Gitea issue.

* **`status:triage`**
  * Proposed Description: Issue needs human or orchestrator triage
  * Proposed Color: `fbca04`
  * Use: Used for incoming issues (especially automated ones like `source:glitchtip`) that have not yet been evaluated for priority or resolution.