Wave 5: Label Color Consistency Audit Report

.github/issue-types.yml

@@ -83,3 +83,9 @@ issue_types:
   - name: Support
     color: 0E8A16
     label: type:support
+  - name: Help
+    color: 0E8A16
+    label: type:help
+  - name: User Experience Feedback
+    color: "5319E7"
+    label: type:ux-feedback

.github/labels.yml

@@ -208,10 +208,6 @@
   aliases:
     - audit
 
-- name: type:qa
-  color: D29922
-  description: "Quality assurance"
-
 - name: type:review
   color: 4393F8
   description: "Code or design review task"
@@ -236,6 +232,19 @@
   aliases:
     - support
 
+- name: type:help
+  color: 0E8A16
+  description: "Help request"
+  aliases:
+    - help
+
+- name: type:ux-feedback
+  color: "5319E7"
+  description: "User experience feedback"
+  aliases:
+    - ux-feedback
+    - user-experience-feedback
+
 # --- Meta / housekeeping ---
 
 - name: meta:needs-changelog

.github/metrics/meta.json

@@ -4,4 +4,4 @@
   "changes": 2,
   "errors": 0,
   "optouts": 0
-}
+}

.github/projects/PLANNING_TEMPLATE.md

@@ -1,9 +1,10 @@
 ---
+file_type: documentation
 title: "Project Planning Template"
 description: "Use this template to document planning before creating related issues"
-file_type: "documentation"
-created_date: "YYYY-MM-DD"
-version: '1.0.1'
+created_date: "2026-05-31"
+last_updated: "2026-06-01"
+version: "1.0.1"
 author: "LightSpeed Team"
 maintainer: "LightSpeed Team"
 owners: ["lightspeedwp/maintainers"]
@@ -174,9 +175,9 @@ Brief 2-3 sentence summary of the project's purpose, scope, and business/technic
 
 **GitHub issues, PRs, discussions, or external links**
 
-- Related issue: [#123 - Issue title](https://github.com/lightspeedwp/.github/issues/123)
-- Blocking issue: [#124 - Issue title](https://github.com/lightspeedwp/.github/issues/124)
-- Blocked by: [#125 - Issue title](https://github.com/lightspeedwp/.github/issues/125)
+- Related issue: #XXX - [Issue title]
+- Blocking issue: #XXX - [Issue title]
+- Blocked by: #XXX - [Issue title]
 - Reference: [Link to spec, design doc, or external resource]
 
 ---

.github/projects/active/DOCUMENTATION_AUDIT_PROMPT_COMPREHENSIVE.md

@@ -1,12 +1,13 @@
 ---
-file_type: "planning-document"
+file_type: documentation
 title: "Comprehensive Documentation & Automation Audit Prompt"
 description: "Detailed step-by-step prompt for creating GitHub issues to audit and fix documentation, templates, labeling, and automation systems"
-version: "1.0.0"
+version: "1.0.1"
 created_date: "2026-05-31"
-last_updated: '2026-06-01'
-status: "ready-for-execution"
-owner: "LightSpeed Team"
+last_updated: "2026-06-01"
+status: active
+owners:
+  - lightspeedwp/maintainers
 ---
 
 # Comprehensive Documentation & Automation Audit Prompt
@@ -156,7 +157,7 @@ See child issues for detailed audits of:
 - `.github/issue-types.yml`
 - `.github/issue-fields.yml`
 - `docs/LABEL_STRATEGY.md`
-- `docs/ISSUE_LABELS.md`
+- `docs/LABELING.md`
 - `docs/ISSUE_TYPES.md`
 - `docs/ISSUE-FIELDS.md`
 ```
@@ -504,7 +505,7 @@ For each parent issue above, create the following child issues using this templa
 
 - Review all files related to issue creation:
   - `docs/ISSUE_CREATION_GUIDE.md`
-  - `docs/ISSUE_LABELS.md`
+  - `docs/LABELING.md`
   - `docs/ISSUE_TYPES.md`
   - `.github/ISSUE_TEMPLATE/README.md`
   - `docs/index.md` (if references issues)
@@ -523,7 +524,7 @@ For each parent issue above, create the following child issues using this templa
 
 - Review all files related to PR creation:
   - `docs/PR_CREATION_PROCESS.md`
-  - `docs/PR_LABELS.md`
+  - `docs/LABELING.md`
   - `.github/PULL_REQUEST_TEMPLATE/README.md`
   - `instructions/pull-requests.instructions.md`
   - `docs/BRANCHING_STRATEGY.md`
@@ -541,9 +542,9 @@ For each parent issue above, create the following child issues using this templa
 - Review all files related to labeling:
   - `docs/LABEL_STRATEGY.md`
   - `docs/LABELING.md`
-  - `docs/ISSUE_LABELS.md`
-  - `docs/PR_LABELS.md`
-  - `docs/AUTOMATION_GOVERNANCE.md` (label section)
+  - `docs/LABELING.md`
+  - `docs/LABELING.md`
+  - `docs/AUTOMATION.md` (label section)
   - Agent specs for labeling
 - Identify duplication and overlap
 - Propose single source of truth for labeling
@@ -772,7 +773,7 @@ gh issue create \
 
 - `CLAUDE.md` — Repository boundaries and structure
 - `docs/LABEL_STRATEGY.md` — Label philosophy and strategy
-- `docs/AUTOMATION_GOVERNANCE.md` — Automation standards
+- `docs/AUTOMATION.md` — Automation standards
 - `.github/labels.yml` — Canonical label definitions
 - `.github/issue-types.yml` — Canonical issue type definitions
 

.github/projects/active/wave-5-documentation-audit/INDEX.md

@@ -1,9 +1,11 @@
 ---
+file_type: documentation
 title: "Wave 5 Documentation Audit - Issue Index"
 description: "Complete index of all parent and child issues for the Documentation Audit project"
-version: '1.0.1'
+version: "1.0.1"
 created_date: "2026-05-31"
-status: "ready-for-review"
+last_updated: "2026-06-01"
+status: active
 ---
 
 # Wave 5 Documentation Audit — Issue Index

.github/projects/active/wave-5-documentation-audit/children/01-1-template-inventory.md

@@ -1,13 +1,13 @@
 ---
 issue_number: 654
-file_type: "task"
+file_type: documentation
 description: "Inventory and audit of issue templates for standardization"
 parent_issue: 649
 title: "[Child of #649] Audit: Issue Template Inventory & Standardization"
 type: "type:audit"
 area: "area:documentation"
 priority: "priority:normal"
-status: "status:needs-triage"
+status: draft
 effort: "S"
 ---
 

.github/projects/active/wave-5-documentation-audit/children/01-2-audit-report-issue-creation.md

@@ -1,10 +1,10 @@
 ---
-file_type: "documentation"
+file_type: documentation
 title: "Issue Creation Documentation Consolidation Audit"
 description: "Complete audit of issue creation documentation identifying consolidation opportunities and duplicated content"
-version: "v1.0"
+version: "v1.0.1"
 created_date: "2026-05-31"
-last_updated: '2026-06-01'
+last_updated: "2026-06-01"
 author: "Claude Code"
 maintainer: "LightSpeedWP Team"
 tags: ["documentation", "audit", "consolidation", "wave-5"]
@@ -28,7 +28,7 @@ Audited 6 documentation files related to issue creation. Found:
 
 - **Significant overlap** between `instructions/issues.instructions.md` and `docs/ISSUE_CREATION_GUIDE.md`
 - **Internal duplication** within `instructions/issues.instructions.md` itself (content repeats)
-- **Missing file** (`docs/ISSUE_LABELS.md` referenced in audit scope but does not exist)
+- **Missing file** (`docs/LABELING.md` referenced in audit scope but does not exist)
 - **Fragmented responsibility** across 4 active files covering similar ground
 
 **Recommendation:** Consolidate into 2 canonical files (instructions + guide) and create a single reference for labels.
@@ -40,7 +40,7 @@ Audited 6 documentation files related to issue creation. Found:
 | File | Path | Exists | Status | Role |
 |------|------|--------|--------|------|
 | Issue Creation Guide | `docs/ISSUE_CREATION_GUIDE.md` | ✅ | Active | High-level how-to |
-| Issue Labels Guide | `docs/ISSUE_LABELS.md` | ❌ | Missing | Supposed label reference |
+| Issue Labels Guide | `docs/LABELING.md` | ❌ | Missing | Supposed label reference |
 | Issue Types Reference | `docs/ISSUE_TYPES.md` | ✅ | Active | Canonical type definitions |
 | Issue Templates README | `.github/ISSUE_TEMPLATE/README.md` | ✅ | Active | Template directory guide |
 | Issue Instructions | `instructions/issues.instructions.md` | ✅ | Active | Official instructions (AI/agents) |
@@ -79,7 +79,7 @@ Audited 6 documentation files related to issue creation. Found:
 
 ---
 
-### 2. **`docs/ISSUE_LABELS.md`**
+### 2. **`docs/LABELING.md`**
 
 **Status:** ❌ **DEPRECATED & CONSOLIDATED**
 
@@ -203,7 +203,7 @@ Instead of creating a new file, update all broken references to `ISSUE_LABELS.md
 | Current File | Content | Proposed Location | Action | Rationale |
 |--------------|---------|-------------------|--------|-----------|
 | `docs/ISSUE_CREATION_GUIDE.md` | Practical how-to guide | Keep (docs/) | Preserve | Good audience fit, clear structure |
-| `docs/ISSUE_LABELS.md` | Deprecated; consolidated into LABELING.md | Update references | Fix broken links | Already exists at `docs/LABELING.md#issue-labelling`; redirect references there |
+| `docs/LABELING.md` | Deprecated; consolidated into LABELING.md | Update references | Fix broken links | Already exists at `docs/LABELING.md#issue-labelling`; redirect references there |
 | `docs/ISSUE_TYPES.md` | Type definitions & reference | Keep (docs/) | Preserve | Comprehensive, well-maintained |
 | `.github/ISSUE_TEMPLATE/README.md` | Template directory guide | Migrate to inline comments | Archive or migrate | Mostly metadata; can live in directory |
 | `instructions/issues.instructions.md` | Official instructions | Refactor | Consolidate & fix | Remove internal duplication; keep authoritative core |
@@ -249,7 +249,7 @@ Instead of creating a new file, update all broken references to `ISSUE_LABELS.md
 - `docs/ISSUE_CREATION_GUIDE.md` (section 4, sparse)
 - `instructions/issues.instructions.md` (section 4–5, references missing files)
 - `docs/ISSUE_TYPES.md` (type-focused, doesn't cover label families)
-- Missing: `docs/ISSUE_LABELS.md` (should exist but doesn't)
+- Missing: `docs/LABELING.md` (should exist but doesn't)
 
 **Content:** What labels are required, label families, one-hot rules
 
@@ -275,7 +275,7 @@ Instead of creating a new file, update all broken references to `ISSUE_LABELS.md
 
 ### Critical Gaps
 
-1. **Broken references to `docs/ISSUE_LABELS.md`**
+1. **Broken references to `docs/LABELING.md`**
    - `instructions/issues.instructions.md` section 4 references deprecated file
    - File was consolidated into `docs/LABELING.md` (per `instructions/DEPRECATED.md`)
    - References should point to `docs/LABELING.md#issue-labelling` instead
@@ -304,7 +304,7 @@ Instead of creating a new file, update all broken references to `ISSUE_LABELS.md
    - Preserve formatting and structure
 
 2. **Update broken references to ISSUE_LABELS.md**
-   - Locate all references to the deprecated `docs/ISSUE_LABELS.md`
+   - Locate all references to the deprecated `docs/LABELING.md`
    - Redirect them to `docs/LABELING.md#issue-labelling` instead
    - Note: The file was consolidated into `docs/LABELING.md` (see `instructions/DEPRECATED.md`)
    - Do NOT recreate the deprecated file
@@ -346,7 +346,7 @@ Instead of creating a new file, update all broken references to `ISSUE_LABELS.md
 |--------|-------|
 | Files audited | 6 |
 | Files with duplicates | 1 (`instructions/issues.instructions.md`) |
-| Missing files | 1 (`docs/ISSUE_LABELS.md`) |
+| Missing files | 1 (`docs/LABELING.md`) |
 | Empty files | 1 (`docs/index.md`) |
 | Overlapping content areas | 4 |
 | Total lines across all files | ~717 |

.github/projects/active/wave-5-documentation-audit/children/01-2-template-automation-mapping.md

@@ -1,13 +1,13 @@
 ---
 issue_number: 655
-file_type: "task"
+file_type: documentation
 description: "Map issue templates to their automation triggers"
 parent_issue: 649
 title: "[Child of #649] Audit: Issue Template → Automation Trigger Mapping"
 type: "type:audit"
 area: "area:automation"
 priority: "priority:normal"
-status: "status:needs-triage"
+status: draft
 effort: "M"
 ---
 
@@ -48,5 +48,5 @@ Map each issue template to the automation it should trigger and identify gaps be
 ## Related Documentation
 
 - [Label Strategy](https://github.com/lightspeedwp/.github/blob/develop/docs/LABEL_STRATEGY.md)
-- [Automation Governance](https://github.com/lightspeedwp/.github/blob/develop/docs/AUTOMATION_GOVERNANCE.md)
+- [Automation Governance](https://github.com/lightspeedwp/.github/blob/develop/docs/AUTOMATION.md)
 - [Labeling Guide](https://github.com/lightspeedwp/.github/blob/develop/docs/LABELING.md)

.github/projects/active/wave-5-documentation-audit/children/01-3-labeler-rules-audit.md

@@ -1,13 +1,13 @@
 ---
 issue_number: 656
-file_type: "task"
+file_type: documentation
 description: "Audit labeling rules for issue-specific automation"
 parent_issue: 649
 title: "[Child of #649] Audit: Issue Labeling Rules in labeler.yml"
 type: "type:audit"
 area: "area:labels"
 priority: "priority:normal"
-status: "status:needs-triage"
+status: draft
 effort: "M"
 ---
 
@@ -50,4 +50,4 @@ Comprehensive audit of labeling rules in `.github/labeler.yml` to identify issue
 
 - [Label Strategy](https://github.com/lightspeedwp/.github/blob/develop/docs/LABEL_STRATEGY.md)
 - [Labeler Configuration](https://github.com/lightspeedwp/.github/blob/develop/.github/labeler.yml)
-- [Automation Governance](https://github.com/lightspeedwp/.github/blob/develop/docs/AUTOMATION_GOVERNANCE.md)
+- [Automation Governance](https://github.com/lightspeedwp/.github/blob/develop/docs/AUTOMATION.md)

.github/projects/active/wave-5-documentation-audit/children/01-4-ai-instructions.md

@@ -1,13 +1,13 @@
 ---
 issue_number: 657
-file_type: "task"
+file_type: documentation
 description: "Create clear instructions for AI agents on issue creation"
 parent_issue: 649
 title: "[Child of #649] Implement: Clear AI Agent Instructions for Issue Creation"
 type: "type:task"
 area: "area:automation"
 priority: "priority:important"
-status: "status:needs-triage"
+status: draft
 effort: "M"
 ---
 

.github/projects/active/wave-5-documentation-audit/children/02-1-labels-color-consistency.md

@@ -1,13 +1,13 @@
 ---
 issue_number: 658
-file_type: "task"
+file_type: documentation
 description: "Verify label colors follow the documented strategy"
 parent_issue: 650
 title: "[Child of #650] Audit: labels.yml Color Consistency & Strategy Alignment"
 type: "type:audit"
 area: "area:labels"
 priority: "priority:important"
-status: "status:needs-triage"
+status: draft
 effort: "M"
 ---
 
@@ -44,10 +44,10 @@ Verify that all 200+ labels in `labels.yml` follow the documented color strategy
 
 - `.github/labels.yml`
 - `docs/LABEL_STRATEGY.md`
-- `docs/ISSUE_LABELS.md`
+- `docs/LABELING.md`
 
 ## Related Documentation
 
 - [Label Strategy](https://github.com/lightspeedwp/.github/blob/develop/docs/LABEL_STRATEGY.md)
-- [Issue Labels Guide](https://github.com/lightspeedwp/.github/blob/develop/docs/ISSUE_LABELS.md)
+- [Issue Labels Guide](https://github.com/lightspeedwp/.github/blob/develop/docs/LABELING.md)
 - [Canonical Labels File](https://github.com/lightspeedwp/.github/blob/develop/.github/labels.yml)

.github/projects/active/wave-5-documentation-audit/children/02-2-issue-types-mapping.md

@@ -1,13 +1,13 @@
 ---
 issue_number: 659
-file_type: "task"
+file_type: documentation
 description: "Verify issue types align with templates and labels"
 parent_issue: 650
 title: "[Child of #650] Audit: Issue Types Alignment with Templates & Labels"
 type: "type:audit"
 area: "area:labels"
 priority: "priority:important"
-status: "status:needs-triage"
+status: draft
 effort: "M"
 ---
 
@@ -51,5 +51,5 @@ Verify that all issue types in `issue-types.yml` have matching templates and lab
 ## Related Documentation
 
 - [Issue Types Guide](https://github.com/lightspeedwp/.github/blob/develop/docs/ISSUE_TYPES.md)
-- [Issue Labels Guide](https://github.com/lightspeedwp/.github/blob/develop/docs/ISSUE_LABELS.md)
+- [Issue Labels Guide](https://github.com/lightspeedwp/.github/blob/develop/docs/LABELING.md)
 - [Issue Templates](https://github.com/lightspeedwp/.github/blob/develop/.github/ISSUE_TEMPLATE/README.md)