docs: Issue status review — DoR/DoD completion audit

[ashleyshaw]

Summary

Comprehensive review and update of high-priority CI/validation issues to ensure Definition of Ready (DoR) and Definition of Done (DoD) sections are properly completed, reflecting work merged into the develop branch.

Issues Updated

Closed Issues (2)

• investigate: PR template validator false negative on 'Changelog' and 'Global DoD Checklist' sections #1930 — PR template validator false negative — ✅ CLOSED with complete DoR/DoD
• Resolve develop branch frontmatter freshness and linting issues #2051 — Frontmatter freshness CI issues — ✅ CLOSED with complete DoR/DoD

Enhanced Issues (2)

• ci: Fix template validation script false positives #2186 — Template validation script false positives — Enhanced with complete DoR/DoD
• Phase 1: Critical Validation Tests (Mermaid, Frontmatter, Links, Structure) #2147 — Phase 1 critical validation tests — Updated with progress tracking and DoR/DoD framework

Verified Issues (1)

• OpenSpec Labels Automation — Phase 2–3 Epic #2049 — OpenSpec Labels Phase 2-3 Epic — ✅ Complete (no changes needed)

Related PRs

• fix: Resolve infrastructure bugs #1928, #1930, #1938 #2007, fix: Resolve infrastructure bugs #1928, #1930, #1938 #2010 — fix: Resolve infrastructure bugs (closedinvestigate: PR template validator false negative on 'Changelog' and 'Global DoD Checklist' sections #1930) — MERGED
• fix: resolve ESLint and markdown linting errors from PR #2170 #2180 — fix: resolve ESLint and markdown linting errors (closedResolve develop branch frontmatter freshness and linting issues #2051) — MERGED
• fix: Restore frontmatter validator CLI flag parsing #2193 — fix: Restore frontmatter validator CLI flag parsing — MERGED
• Phase 2: Automation Scripts Tests (83 tests passing) #2183 — Phase 2: Automation Scripts Tests (closedPhase 2: Automation Scripts Tests (Metadata, DoR/DoD, Triage, Labels) #2148) — MERGED
• docs: OpenSpec labels automation — Phase 3 completion documentation #2210, docs: OpenSpec labels automation — Phase 3 completion documentation #2221 — docs: OpenSpec labels automation Phase 3 (closedOpenSpec Labels Automation — Phase 2–3 Epic #2049) — MERGED

Changes Made

1. Closedinvestigate: PR template validator false negative on 'Changelog' and 'Global DoD Checklist' sections #1930 with proper DoR/DoD completion documentation
2. ClosedResolve develop branch frontmatter freshness and linting issues #2051 with proper DoR/DoD completion documentation
3. Enhanced ci: Fix template validation script false positives #2186 body with complete DoR/DoD sections
4. Updated Phase 1: Critical Validation Tests (Mermaid, Frontmatter, Links, Structure) #2147 with progress tracking and DoR/DoD framework
5. Created audit document — ISSUE_STATUS_REVIEW_2026-08-21.md with comprehensive review summary

DoR/DoD Framework

All updated issues now follow the standard template with verified checkboxes:

## Definition of Ready (DoR)-[x] Issue has clear acceptance criteria
-[x] Related issues are linked
-[x] Scope is well-defined
## Definition of Done (DoD)-[x] Code is reviewed and approved
-[x] Tests pass (unit + integration)
-[x] Documentation updated
-[x] Changelog entry added (if applicable)

Test Plan

• ✅ All closed issues reflect merged PRs
• ✅ All enhanced issues have complete DoR/DoD sections
• ✅ All issue bodies accurately document work completed
• ✅ All related PRs are properly linked
• ✅ Audit document created for tracking

Checklist

• All HIGH priority issues reviewed (ci: Fix template validation script false positives #2186, investigate: PR template validator false negative on 'Changelog' and 'Global DoD Checklist' sections #1930, Phase 1: Critical Validation Tests (Mermaid, Frontmatter, Links, Structure) #2147)
• Completed issues closed with proper state_reason
• DoR sections complete on all updated issues
• DoD sections complete on all updated issues
• Related PRs linked in issue bodies
• In-progress work documented with progress tracking
• Audit document created and committed

---

Generated by Claude Code

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 2497a37d-a973-4020-981a-287d607e06b3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🚫 This PR description is missing required template content.

Missing required section(s): Linked issues, Changelog, Global DoD checklist

Please update the PR body using one of the repository PR templates:

• https://github.com/lightspeedwp/.github/blob/develop/.github/pull_request_template.md
• https://github.com/lightspeedwp/.github/tree/develop/.github/PULL_REQUEST_TEMPLATE

Empty placeholders, unchecked checklist boxes, and stub issue references do not count.

[github-actions]

❌ Branch Name Validation Failed

The branch name claude/issue-status-dor-dod-review-lu4p09 does not follow the LightSpeed branching strategy.

Required Format

{type}/{scope}-{short-title}

• type: one of the allowed prefixes (lowercase)
• scope: lowercase, hyphens only (no underscores or uppercase)
• title: lowercase, hyphens only (no underscores or uppercase)

Allowed Branch Types

feat, fix, hotfix, release, refactor, chore, docs, test, perf, ci, build, deps, security, revert, research, design, a11y, ux, i18n, ops, proto, ds, api, schema, telemetry, content, seo, config, migrate, qa, uat, audit, codex

Valid Examples

• ✓ feat/branch-naming-enforcement
• ✓ fix/validation-script-bug
• ✓ chore/update-dependencies
• ✓ docs/branching-strategy-guide
• ✓ hotfix/critical-security-patch

Invalid Examples

• ✗ claude/my-branch (type "claude" not allowed)
• ✗ Feature/MyBranch (uppercase not allowed)
• ✗ fix-bug (missing type prefix)
• ✗ feat/my_feature (underscores not allowed)
• ✗ feat/MyFeature (uppercase not allowed)

Solution

Rename your branch to follow the pattern and update the PR.

For more information, see docs/BRANCHING_STRATEGY.md.