docs: add Phase 4 governance deployment planning and issues

.github/projects/active/ai-governance-audit-implementation/PLANNING.md

@@ -326,6 +326,104 @@ Week 3:
 
 ---
 
+## PHASE 4: Deploy & Enforce Governance Rules Organization-Wide
+
+**Phase 4 Overview:** Extend governance rules to the entire organization, establish enforcement policy, train teams, and set up compliance tracking.
+
+**Duration:** 2-3 weeks  
+**Milestone:** `v1.2`  
+**Status:** In Progress (5 issues created 2026-09-03)
+
+### Phase 4 Issues
+
+#### Issue 4.1: Migrate Governance Rules to Core Organization Repositories
+- **Issue:** [#2663](https://github.com/lightspeedwp/.github/issues/2663)
+- **Type:** `feat`
+- **Scope:** automation
+- **Template:** Feature
+- **Labels:** `type:feat`, `area:automation`, `area:governance`, `priority:high`, `status:needs-triage`
+- **Effort:** 3-4 hours
+- **Deliverables:**
+  - Deploy `.github/workflows/validate-branch-name.yml` to sister repos
+  - Configure PR template resolver for consistent routing
+  - Enable title normalization automation
+  - Document migration steps and validation
+- **Success Criteria:** Branch validation passing on all target repos, zero manual workarounds
+
+#### Issue 4.2: Establish Organization-Wide Branch Naming Enforcement Policy
+- **Issue:** [#2664](https://github.com/lightspeedwp/.github/issues/2664)
+- **Type:** `feat`
+- **Scope:** governance
+- **Template:** Feature
+- **Labels:** `type:feat`, `area:governance`, `area:docs`, `priority:high`, `status:needs-triage`
+- **Effort:** 4-5 hours
+- **Deliverables:**
+  - Create `docs/ORG_GOVERNANCE_POLICY.md` with complete policy
+  - Document allowed types (33), forbidden prefixes
+  - Establish exceptions and override procedures
+  - Define escalation path for violations
+- **Success Criteria:** Policy documented, all org repos aware, team acknowledgment > 90%
+
+#### Issue 4.3: Create Team Onboarding and Training Documentation
+- **Issue:** [#2665](https://github.com/lightspeedwp/.github/issues/2665)
+- **Type:** `feat`
+- **Scope:** docs
+- **Template:** Documentation
+- **Labels:** `type:feat`, `area:docs`, `area:automation`, `priority:high`, `status:needs-triage`
+- **Effort:** 3-4 hours
+- **Deliverables:**
+  - `docs/DEVELOPER_ONBOARDING.md` — step-by-step guide
+  - `docs/BRANCH_NAMING_QUICK_REFERENCE.md` — quick reference
+  - FAQs, troubleshooting, success examples
+  - Rollout schedule with enforcement timeline
+- **Success Criteria:** > 90% developer adoption within 2 weeks, > 95% documentation completeness
+
+#### Issue 4.4: Set Up Governance Compliance Reporting and Metrics Dashboard
+- **Issue:** [#2666](https://github.com/lightspeedwp/.github/issues/2666)
+- **Type:** `feat`
+- **Scope:** automation
+- **Template:** Feature
+- **Labels:** `type:feat`, `area:automation`, `area:governance`, `priority:normal`, `status:needs-triage`
+- **Effort:** 4-5 hours
+- **Deliverables:**
+  - Design metrics framework (compliance rate, CI failures, PR template routing accuracy)
+  - Create reporting dashboard (GitHub Project or GitHub Actions workflow)
+  - Set up automated data collection and reporting
+  - Generate weekly/monthly reports
+- **Success Criteria:** Dashboard live and updating daily, compliance > 95%, < 5 manual report requests/week
+
+#### Issue 4.5: Define Governance Exceptions and Override Procedures
+- **Issue:** [#2667](https://github.com/lightspeedwp/.github/issues/2667)
+- **Type:** `feat`
+- **Scope:** governance
+- **Template:** Feature
+- **Labels:** `type:feat`, `area:governance`, `area:docs`, `priority:normal`, `status:needs-triage`
+- **Effort:** 2-3 hours
+- **Deliverables:**
+  - Create `docs/GOVERNANCE_EXCEPTIONS.md` with policy
+  - Document exception request process
+  - Create exception tracking mechanism
+  - Establish override procedures for urgent cases
+  - Build appeals process
+- **Success Criteria:** Policy documented, exception request process clear, all exceptions tracked, appeals resolved within 24 hours
+
+---
+
+## Phase 4 Dependencies & Critical Path
+
+```
+4.1 Migration ──┐
+                ├──> 4.4 Reporting (compliance data)
+4.2 Policy ─────┤
+                ├──> 4.5 Exceptions (policy coordination)
+4.3 Training ───┘
+```
+
+**Critical Path:** 4.2 (Policy) → 4.3 (Training) → Org rollout
+**Parallel Work:** 4.1 (Migration) + 4.4 (Reporting) + 4.5 (Exceptions)
+
+---
+
 ## Issue Templates & Labels
 
 **All issues use these labels:**

.github/projects/active/ai-governance-audit-implementation/README.md

@@ -7,15 +7,12 @@ status: in-progress
 
 # AI Governance Audit Implementation — Active Project
 
-**Phase 3 Status:** ✅ **COMPLETE & MERGED** (2026-09-03 @ 03:30 UTC)  
-**Phase 4 Status:** 🚀 **KICKOFF** (2026-09-03)  
-**Branch:** `develop` (Phase 3 merged; Phase 4 in progress)  
-**Milestone Phase 3:** `v1.1` (Complete)  
-**Milestone Phase 4:** `v1.2` (In Progress)  
-**Phase 3 Duration:** 3-4 weeks (Completed)  
-**Phase 4 Duration:** 2-3 weeks (In Progress)  
-**Issues Phase 3:** 15 (ALL COMPLETE & MERGED)  
-**Issues Phase 4:** 5 (In Planning/Kickoff)
+**Status:** ✅ **PHASE 3 COMPLETE** → **PHASE 4 KICKOFF**  
+**Phase 3:** Merged to develop (2026-09-03 @ 03:30 UTC)  
+**Phase 4:** Governance deployment & org-wide rollout  
+**Milestone:** `v1.1` (Phase 3), `v1.2` (Phase 4)  
+**Phase 3 Issues:** 15 (ALL COMPLETE & MERGED)  
+**Phase 4 Issues:** 5 (In Progress)
 
 ---
 
@@ -144,24 +141,42 @@ See **[PHASE_4_STATUS.md](./PHASE_4_STATUS.md)** for detailed real-time tracking
 
 ---
 
-## 🔗 Related Issues
+## 🔗 Related Issues — Phase 3 (COMPLETE)
 
 | Issue | Type | Status |
 |-------|------|--------|
-| [#2396](https://github.com/lightspeedwp/.github/issues/2396) | Epic | In Progress |
-| [#2534](https://github.com/lightspeedwp/.github/issues/2534) | Feature | Ready |
-| [#2535](https://github.com/lightspeedwp/.github/issues/2535) | Feature | Ready |
-| [#2536](https://github.com/lightspeedwp/.github/issues/2536) | Feature | Ready |
-| [#2537](https://github.com/lightspeedwp/.github/issues/2537) | Feature | Ready |
-| [#2538](https://github.com/lightspeedwp/.github/issues/2538) | Feature | Ready |
-| [#2539](https://github.com/lightspeedwp/.github/issues/2539) | Feature | Ready |
-| [#2540](https://github.com/lightspeedwp/.github/issues/2540) | Test | Ready |
-| [#2541](https://github.com/lightspeedwp/.github/issues/2541) | Feature | Ready |
-| [#2542](https://github.com/lightspeedwp/.github/issues/2542) | Feature | Ready |
-| [#2543](https://github.com/lightspeedwp/.github/issues/2543) | Feature | Ready |
-| [#2544](https://github.com/lightspeedwp/.github/issues/2544) | Test | Ready |
-| [#2545](https://github.com/lightspeedwp/.github/issues/2545) | Documentation | Ready |
-| [#2546](https://github.com/lightspeedwp/.github/issues/2546) | Feature | Ready |
+| [#2534](https://github.com/lightspeedwp/.github/issues/2534) | Documentation | ✅ Complete |
+| [#2535](https://github.com/lightspeedwp/.github/issues/2535) | Documentation | ✅ Complete |
+| [#2536](https://github.com/lightspeedwp/.github/issues/2536) | Documentation | ✅ Complete |
+| [#2537](https://github.com/lightspeedwp/.github/issues/2537) | Build & CI | ✅ Complete |
+| [#2538](https://github.com/lightspeedwp/.github/issues/2538) | Build & CI | ✅ Complete |
+| [#2539](https://github.com/lightspeedwp/.github/issues/2539) | Automation | ✅ Complete |
+| [#2540](https://github.com/lightspeedwp/.github/issues/2540) | Testing | ✅ Complete |
+| [#2541](https://github.com/lightspeedwp/.github/issues/2541) | Automation | ✅ Complete |
+| [#2542](https://github.com/lightspeedwp/.github/issues/2542) | Automation | ✅ Complete |
+| [#2543](https://github.com/lightspeedwp/.github/issues/2543) | Documentation | ✅ Complete |
+| [#2544](https://github.com/lightspeedwp/.github/issues/2544) | Testing | ✅ Complete |
+| [#2545](https://github.com/lightspeedwp/.github/issues/2545) | Documentation | ✅ Complete |
+| [#2546](https://github.com/lightspeedwp/.github/issues/2546) | Automation | ✅ Complete |
+
+---
+
+## 🔗 Related Issues — Phase 4 (In Progress)
+
+### 4.1: Governance Rule Migration
+- [#2663](https://github.com/lightspeedwp/.github/issues/2663) — Migrate governance rules to core organization repositories
+
+### 4.2: Organization-Wide Governance Policy
+- [#2664](https://github.com/lightspeedwp/.github/issues/2664) — Establish organization-wide branch naming enforcement policy
+
+### 4.3: Team Training & Rollout
+- [#2665](https://github.com/lightspeedwp/.github/issues/2665) — Create team onboarding and training documentation
+
+### 4.4: Governance Compliance Reporting
+- [#2666](https://github.com/lightspeedwp/.github/issues/2666) — Set up governance compliance reporting and metrics dashboard
+
+### 4.5: Governance Exceptions & Overrides
+- [#2667](https://github.com/lightspeedwp/.github/issues/2667) — Define governance exceptions and override procedures
 
 ---