feat: Add PR automation scripts for label and changelog management

.github/projects/_templates/OPENSPEC_TEMPLATE.md

@@ -54,7 +54,7 @@ Each phase includes:
 
 ## Phase 1: [Phase Name] — Architecture & Design
 
-**Related Planning:** [PLANNING.md — Phase 1](./PLANNING.md#phase-1-phase-name-weeks-xy)
+**Related Planning:** See Phase 1 section in PLANNING.md (created from PLANNING_TEMPLATE.md)
 
 ### 1.1 Architecture Overview
 
@@ -333,7 +333,7 @@ describe('Component A', () => {
 
 ## Phase 2: [Phase Name] — Implementation & Testing
 
-**Related Planning:** [PLANNING.md — Phase 2](./PLANNING.md#phase-2-phase-name-weeks-xy)
+**Related Planning:** See Phase 2 section in PLANNING.md (created from PLANNING_TEMPLATE.md)
 
 [Continue with same pattern for Phase 2]
 
@@ -408,9 +408,11 @@ describe('Component A', () => {
 **Request Example:**
 
 ```bash
+# gitleaks:allow
 curl -X GET \
  https://api.example.com/api/v1/resource/550e8400-e29b-41d4-a716-446655440000 \
  -H 'Authorization: Bearer token123'
+# gitleaks:allowlist
 ```
 
 **Success Response (200 OK):**
@@ -556,9 +558,9 @@ curl -X GET \
 
 ## References & Related Documents
 
-- [PLANNING.md](./PLANNING.md) — Project planning and timeline
-- [GitHub Issues — Master Epic](../../../issues/XXXX) — Issue tracking
-- [Related Architecture Doc](../../../docs/ARCHITECTURE.md) — System architecture
+- PLANNING.md (created from PLANNING_TEMPLATE.md) — Project planning and timeline
+- GitHub Issues — Master Epic (link issue number to your project's master epic issue)
+- Related Architecture Doc — Reference any relevant architecture documentation in your repository
 
 ---
 

CHANGELOG.md

@@ -27,6 +27,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [Unreleased]
 
 ### Added
+- **PR Automation Scripts — update-pr-labels and update-pr-changelog-review** — Two reusable automation scripts for managing PR status labels and changelog requirements. (1) `update-pr-labels-simple.js` provides lightweight label synchronization with minimal API calls, suitable for CI/CD pipelines with limited quota; (2) `update-pr-changelog-review.js` offers full-featured status tracking with review data fetching, label updates, dry-run/interactive/auto modes, and rate limiting. Both scripts include comprehensive test suites (`update-pr-labels-simple.test.js` with 20+ tests, `update-pr-changelog-review.test.js` with 19+ tests) validating status determination, label management, and argument parsing. Features: dry-run mode for safe preview, interactive prompts before changes, automatic mode for batch operations, robust error handling, and extensive documentation. ([PR #2015](https://github.com/lightspeedwp/.github/pull/2015), [#1735](https://github.com/lightspeedwp/.github/issues/1735))
+
 - **OpenSpec Status Labels Phase 2 — Template Validation & Automatic Injection** — Complete implementation of Definition of Ready (DoR) and Definition of Done (DoD) template validation and automatic injection for GitHub issues. Phase 2 deliverables include: (1) Template mapping system (`dor-dod-templates.js`) with 17 issue type templates (task, bug, feature, design, epic, story, improvement, chore, refactor, build-ci, test, performance, a11y, security, documentation, research, audit) containing 85+ total checklist items; (2) Validation & injection script (`validate-inject-dor-dod.js`, 282 LOC) with batch processing (up to 300 issues), dry-run mode, JSON report generation, and 9 CodeRabbit security/quality fixes (--limit validation, exec() null-safety, dry-run tracking, error handling); (3) Comprehensive test suite (43 tests, 100% coverage) validating template structure, DoR/DoD detection, type detection, and edge cases; (4) GitHub Actions workflow (`validate-dor-dod-sections.yml`) with daily schedule and manual trigger supporting dry-run mode; (5) Complete documentation including Phase 2 summary, template validation guide, and Phase 3 handoff. All templates include actionable checklist items tailored to each issue type. Script validates existing issues and automatically injects missing templates based on type label. Dry-run mode allows safe preview of batch operations. ([PR #1986](https://github.com/lightspeedwp/.github/pull/1986), [#1943](https://github.com/lightspeedwp/.github/issues/1943), [OpenSpec Phase 1](https://github.com/lightspeedwp/.github/pull/1985))