feat: Set up governance compliance reporting and metrics dashboard

[ashleyshaw]

Summary

Create dashboards and reporting tools to track governance compliance across the organization in real-time. This enables visibility into Phase 4 rollout success, identifies improvement areas, and helps leadership monitor organizational adoption of governance rules.

Proposed Solution

Design and implement a compliance metrics framework:

1. Metrics Framework

   • Compliance rate: % of branches with correct naming
   • CI failure rate: failures due to invalid branch names
   • PR template routing accuracy: % of PRs with correct template
   • Title normalization success rate: % of issues/PRs properly titled
   • Per-repository compliance breakdown
   • Developer/team compliance scores

2. Reporting Dashboard (Choose 1+)

   • GitHub Project with automation rules
   • Custom GitHub Actions workflow generating reports
   • Metrics dashboard published to README.md
   • Weekly email summary to leadership

3. Data Collection

   • Query GitHub API for branch naming compliance
   • Aggregate validation workflow logs
   • Track PR template routing success via comments
   • Monitor title normalization automation runs
   • Store metrics in time-series format for trend analysis

4. Success Dashboard

   • Visual compliance trend (target: trending to 100%)
   • Per-repository compliance breakdown
   • Developer/team compliance scores
   • Top issues and resolutions
   • Trend analysis (week-over-week, month-over-month)

Acceptance Criteria

• Metrics framework defined and documented
• Reporting dashboard live and updating daily
• Compliance data collection automated
• Real-time visibility into governance adherence
• < 5 manual report requests per week
• Overall compliance > 95%
• Per-repo minimum compliance > 90%
• CI failures due to naming < 1% of all CI runs

Designs / References

• Phase 3 deliverables: validation workflows, automation scripts
• GitHub API documentation for branch/PR/issue queries
• Related issues: feat: Migrate governance rules to core organization repositories #2663 (migration), feat: Establish organization-wide branch naming enforcement policy #2664 (policy)

Testing Approach

1. Set up metrics collection on pilot repo
2. Verify data accuracy against manual spot-checks
3. Test dashboard layout and usability
4. Validate automation reliability
5. Roll out to all target repos
6. Establish baseline metrics
7. Monitor for data quality issues

---

Definition of Ready

• Metrics framework approved by leadership
• Data sources identified and accessible
• Dashboard platform chosen
• Success targets defined

Definition of Done

• Metrics dashboard live and updating daily
• Compliance reporting automated (no manual steps)
• Historical data collected for trend analysis
• Dashboard accessible to team leads/managers
• Initial metrics baseline established
• Monitoring alerts configured (e.g., compliance drops below 90%)
• Documentation for metrics interpretation published

[linear-code]

LS-2985

[github-actions]

⚠️ This issue does not follow a required issue template.

Missing required section(s): Definition of Ready (DoR), Definition of Done (DoD)

The issue will remain open and flagged until the body is corrected.
Please update the issue with one of the official templates:

• https://github.com/lightspeedwp/.github/issues/new/choose

If this was opened by automation, update the automation to preserve the template sections before creating the issue.

[github-actions]

⚠️ Bare Labels Detected

This issue has labels that are not in the canonical taxonomy:

• area:governance
• type:feat

Valid Canonical Labels

Please use labels with a prefix from the canonical taxonomy:

• Type: type:bug, type:feature, type:task, type:documentation, etc.
• Status: status:needs-triage, status:in-progress, status:done, etc.
• Priority: priority:critical, priority:high, priority:normal, priority:low
• Area: area:ci, area:docs, area:labels, area:security, etc.
• Meta: meta:needs-changelog, meta:duplicate, meta:blocked, etc.

For the complete list, see .github/labels.yml.