epic: reviewer-agent - Deliver review orchestration #1802

Overview\n\nMaster epic for Reviewer Agent v2 Implementation — Transform the current reviewer agent into an intelligent multi-tool orchestrator that triggers CodeRabbit, GitHub Code Quality, and GitHub Copilot simultaneously, processes feedback intelligently, and tracks resolution across PR commits.\n\n## Vision\n\nCreate an agent that:\n- Triggers multiple code review tools (CodeRabbit, GitHub Code Quality, GitHub Copilot) in parallel\n- Collects and normalizes feedback from all tools into a unified structure\n- Processes findings intelligently with auto-resolution, false-positive suppression, and escalation logic\n- Tracks resolution progress across multiple PR commits until critical/major issues are addressed\n- Serves organization-wide with config-driven customization for control-plane, WordPress plugins, and WordPress themes\n\n## Expected Outcomes\n\n✅ 40% reduction in manual code review burden \n✅ Critical security/architectural issues never merge unresolved \n✅ Organization-wide reuse across LightSpeedWP repos \n✅ < 5% false positive rate \n✅ Review completion time < 5 minutes \n\n## Planning Phase (Complete)\n\n- ✅ 6 key design decisions documented\n- ✅ Best-practice answers for clarifying questions\n- ✅ Detailed 4-week implementation roadmap\n- ✅ 15 concrete tasks with acceptance criteria\n- ✅ Risk mitigation & success criteria\n- ✅ Planning PR: #1798\n\nPlanning Documentation: See \n\n## Implementation Phases\n\n### Phase 2: Core Implementation (Weeks 1-2)\n- Orchestrator module (tool selection, parallel triggering, polling)\n- Tool integration modules (CodeRabbit, Code Quality, Copilot)\n- Feedback processor (normalization, structuring)\n- State manager (persistence, cycle tracking)\n- Decision engine (auto-resolve, suppress, escalate)\n- Configuration system\n\nSubtasks: (To be created from task breakdown)\n- [ ] Task 1: Create Orchestrator Module\n- [ ] Task 2: Create Tool Integration Modules\n- [ ] Task 3: Create State Manager\n- [ ] Task 4: Create Feedback Processor\n- [ ] Task 5: Create Decision Engine\n- [ ] Task 6: Create Comment Generator\n- [ ] Task 7: Create Configuration System\n- [ ] Task 8: Create Main Agent Entry Point\n\n### Phase 3: Testing & Validation (Week 3)\n- Unit test suite (90% coverage)\n- Integration tests (happy-path)\n- E2E tests (main workflow)\n- Bug fixes & refinement\n\nSubtasks: (To be created)\n- [ ] Task 9: Unit Test Suite\n- [ ] Task 10: Integration Tests\n- [ ] Task 11: E2E Tests\n- [ ] Task 12: Bug Fixes & Refinement\n\n### Phase 4: Documentation & Rollout (Week 4)\n- Architecture documentation with Mermaid diagrams\n- Setup & user guides\n- Rollout planning (alpha → beta → production)\n\nSubtasks: (To be created)\n- [ ] Task 13: Architecture & Technical Documentation\n- [ ] Task 14: Setup & User Guides\n- [ ] Task 15: Rollout Planning & Execution\n\n## Key Design Decisions\n\n1. Agent Scope: One unified agent with configuration overlays (GitHub, WordPress plugin, WordPress theme)\n2. Authorization: Hybrid tokens (org-wide + per-repo override + GitHub-native fallback)\n3. WordPress Support: Optional per-repo (WPCS, PHP, hooks, i18n, theme.json)\n4. Testing: Three-tier strategy (Unit 90% + Integration + E2E)\n5. Documentation: Comprehensive with 8 Mermaid diagrams\n6. Location: Split (planning in , code in )\n\nFull rationale: See \n\n## Technical Details\n\nFile Structure:\n\n\nTechnology Stack:\n- JavaScript (Node.js, ESM modules)\n- Jest for testing (90% coverage target)\n- @actions/core & @actions/github for GitHub integration\n- Existing test patterns from labeling/release agents\n- Existing test helpers from \n\n## Timeline\n\n- Week 1-2: Phase 2 Core Implementation (80 hours)\n- Week 3: Phase 3 Testing & Validation\n- Week 4: Phase 4 Documentation & Rollout\n- Target Merge: 2026-08-26\n\n## Related Issues\n\n- Planning PR: #1798\n- Planning Documentation: \n\n## Success Criteria\n\n- ✅ All 6 design decisions implemented\n- ✅ 90% unit test coverage\n- ✅ Happy-path integration tests passing\n- ✅ E2E workflow proves end-to-end functionality\n- ✅ Documentation complete with diagrams\n- ✅ Zero critical security findings\n- ✅ False positive rate < 5%\n- ✅ Review completion time < 5 minutes\n- ✅ Successful production rollout\n\n## Labels\n\nType: epic \nArea: automation \nPriority: high \nStatus: planning-complete \n\n---\n\nNext: Create 15 subtask issues from Phase 2, 3, 4 task breakdown\n\n## Definition of Ready (DoR)\n\n- [ ] Issue has clear acceptance criteria\n- [ ] Related issues are linked\n- [ ] Scope is well-defined\n\n## Definition of Done (DoD)\n\n- [ ] Code is reviewed and approved\n- [ ] Tests pass (unit + integration)\n- [ ] Documentation updated\n- [ ] Changelog entry added (if applicable)