[Wave 5.2.3] Standardize Issue-Type Naming

[ashleyshaw]

Overview

Align issue-types.yml naming with canonical label definitions to eliminate inconsistencies and reduce confusion.

Context

Wave 5.2 audit identified naming inconsistencies:

• "Code Refactor" (issue-types) vs "type:refactor" (label)
• "Build & CI" (inconsistent capitalization)
• "A11y" (abbreviation) vs "Accessibility" (full name)

Acceptance Criteria

• Naming audit completed for all 25 issue types
• Inconsistencies identified and prioritized
• issue-types.yml updated for consistency
• Labels verified to match (type:* labels)
• Documentation updated with naming guidelines

Technical Details

Decision tree:

1. Use label name as canonical source of truth
2. Full names preferred over abbreviations (Accessibility, not A11y)
3. Consistent capitalization (Build & CI as model)
4. No vendor names without prefix (not just "CI", but "Build & CI")

Effort Estimate

• 1 hour

Related

• Parent: [Audit] Canonical Config Files (labels, issue-types, issue-fields) #650 (Wave 5.2: Canonical Config Files Audit)
• Depends on: None
• Blocks: 5.2.4 (Documentation Updates)

---

Generated by Claude Code
https://claude.ai/code/session_01QBPjNAFgVUmE7RP658hut9"

[linear-code]

LS-850