Make default issue-form labels portable across repositories #2

Maturity context

• Project maturity: developing (51/100)
• Dimension: backlog_governance
• Priority: high

Evidence

• .github/ISSUE_TEMPLATE/task.yml declares labels: [task]
• T50-Systems/.github has no task label
• T50-Systems/t50-systems has no task label

Scope

• Define the organization-wide labels required by inherited issue forms.
• Either remove nonportable automatic labels or add a read-only audit that identifies repositories missing required labels.
• Document how repository-specific forms and taxonomies may override organization defaults.
• Add a maintenance procedure for rolling out any future required label.

Acceptance criteria

• Every label named by a default issue form is present in every in-scope issue-enabled repository or the form no longer requires it.
• The audit reports repository and missing label without mutating repositories.
• The documented override path explains how a repository opts into a different taxonomy.
• A test fixture proves missing-label drift is detected.

Help wanted

Good governance/automation task; organization owners should decide the canonical taxonomy before rollout.

Generated from the repository maturity assessment dated 2026-07-11. Do not include credentials, customer data, or local-only files in public discussion.