epic: label-governance - Stabilise canonical labels and harden workflow automation #449

Epic Summary

Stabilise label governance by resolving orphan labels, enforcing canonical label definitions, and hardening workflow policies that consume label metadata.

The epic also tracks the Audit routing and Review title-handling correction in #3737. This description update does not authorise implementation or locked-configuration changes.

Linked Child Issues/Stories/Tasks/PRs

Current child issues

• #3554 — Canonical conflict-resolution labels and approval-gate policy.
• #3737 — Align Audit routing and Review title handling.

Original related work

• #95 — Orphan labels audit and remediation.
• #66 — Canonical labels and seeding workflow.
• #67 — README regeneration scoping and concurrency guard.
• #69 — CodeRabbit-before-Copilot review order enforcement.

These four original issues are closed. Their historical closure does not establish completion of the reopened epic or its current children.

Milestones & Timeline

The existing GitHub milestone is v1.3. No new milestone, deadline or estimate is proposed.

The original sequencing placed #95 before #66, #67 and #69. Current child dependencies remain defined in their own issues.

For #3737, any separately approved metadata correction on PR #3725 must follow the fix’s merge.

Acceptance Criteria

• Orphan label set is remediated and documented.
• Canonical label source of truth and seeding workflow are aligned.
• README regeneration automation is scoped to changed paths and race-safe.
• Review order policy is codified and validated in workflows.
• The Audit routing and Review title-handling acceptance criteria in fix: label-governance - Align Audit routing and Review title handling #3737 are met.
• All linked stories/tasks completed
• Documentation and changelog updated
• Tests/QA complete
• PR description updated with relevant details
• Changelog entry prepared for PR (if applicable)
• Labels/types match org standards

Criteria remain unchecked; this update does not claim completed implementation, QA or approval.

Dependencies / Blockers

• The original cleanup dependency required current inventory output from 🏷️ Orphan Labels Detected (30) #95. Its historical audit does not establish a fresh inventory for further cleanup.
• Workflow validation in CI-compatible local commands remains required.
• chore: labels - Add conflict-resolution labels to canonical taxonomy [LABEL-UPDATE-REQUEST] #3554 contains separate approval and delivery requirements for locked canonical-label changes.
• fix: label-governance - Align Audit routing and Review title handling #3737 does not authorise locked taxonomy or template edits, new review/ branches, or the separate PR audit: label-consolidation - Export Linear labels and draft Stage 1 change requests #3725 metadata change.
• Chris has been asked to review the child and parent. No completed review is recorded by this update.

Additional Context

The original description assigns this epic to .github/projects/active/label-governance-stabilisation-2026-05-27/.

That directory was not found on current develop. The reference is retained for traceability; its current location requires confirmation.

The epic was historically reported complete in May 2026, but is currently open with active children. Historical inventory counts and completion comments are not current validation.

This concerns repository governance and automation, not a WordPress application runtime. Locked taxonomy and template files are not being edited.

Definition of Ready (DoR)

• Epic goal and scope defined
• Linked stories/tasks listed
• Milestones and timeline mapped
• Dependencies/blockers identified
• Estimate added (if applicable)
• Stakeholders/approvers listed
• Success criteria and measurable outcomes documented
• Timeline and resource estimates provided
• Stakeholder alignment confirmed

Definition of Done (DoD)

• Approved by at least one maintainer
• All linked stories/tasks completed and closed
• Documentation/changelog updated
• QA and testing complete
• All child issues closed before epic can be closed
• Epic issue must be updated with latest status before being closed
• Epic acceptance criteria met
• Epic documentation and summary updated
• Release notes and announcement prepared
• Post-launch monitoring and support plan in place
• Retrospective completed (if applicable)