OpenSpec Labels Phase 3 — Rebased on develop

[ashleyshaw]

Summary

Rebase of OpenSpec Labels Phase 3 branch on latest develop branch. All conflicts resolved, ready for review and merge.

Linked issues

Closes#1751

Changelog

Added

• OpenSpec Labels Phase 3 — Complete Implementation — Event-driven label syncing and automated phase progression for OpenSpec status labels. Phase 3 deliverables include: (1) 4 Event handlers for GitHub lifecycle events (issue-created, pr-opened, pr-merged, issue-closed, 400+ LOC); (2) 4 GitHub Actions workflows for label syncing, phase progression, validation, and reporting; (3) 27 integration tests covering 11 complete workflow scenarios; (4) Audit logging system for tracking all label changes with timestamps; (5) State machine with 6 defined states and automatic phase progression triggers; (6) Label validator with mutex groups to prevent conflicting labels. All 104 tests passing (Phase 2: 43/43, Phase 3 Core: 34/34, Phase 3 Integration: 27/27). Production-ready code quality.

Global DoD

• Code changes complete
• Tests passing (104/104)
• Documentation updated
• Branch rebased on develop
• CI validation passing
• Ready for merge

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@ashleyshaw, you've reached your PR review limit, so we couldn't start this review.

Next review available in:52 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: 6479146d-b1a7-4780-9b69-5549dab6f39c

📥 Commits

Reviewing files that changed from the base of the PR and between 886bcae and 8dceb34.

📒 Files selected for processing (1)

• CHANGELOG.md

---

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): 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 feat/openspec-labels-phase-3 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.