chore: Update active projects status for all 67 initiatives (2026-08-21)

[ashleyshaw]

Chore Pull Request

This repository enforces changelog, release, and label automation for all PRs and issues.
See the organisation-wide Automation Governance & Release Strategy for required rules.

Linked issues

Closes #2282

Summary

Comprehensive status review and update of all 67 active projects in .github/projects/active/. All projects analyzed, categorized by status, and indexed in the main active projects README.

Changes

• active/README.md (v2.4 → v2.5)

  • Added comprehensive status table organizing all 67 projects by category
  • Organized by status: complete (10), active-ready (12), in-progress (35), critical (1), blocked (3), planning (4), transitioning (2)
  • Added priority action items section with TODAY, THIS WEEK, and UPCOMING milestones
  • Added detailed project maintenance checklist (weekly, monthly, quarterly)
  • Updated last_updated to 2026-08-21 (18:00 UTC)

• README.md (v2.0.0 → v2.1.0)

  • Updated version to 2.1.0
  • Updated last_updated to 2026-08-21
  • References comprehensive active project index

Impact / Compatibility

• Runtime/behaviour changes: None
• Build/dev-experience impact: Improved project visibility and status tracking for all 67 active initiatives

Verification

• All 67 active projects analyzed and status determined
• Projects organized by status category and completion percentage
• Priority actions identified and documented
• Maintenance checklist created for ongoing updates
• Related index documentation updated

Risk & Rollback

• Risk level: Low
• Rollback plan: Revert commit to previous version

Key Findings

Status Breakdown (2026-08-21)

Status	Count	Percentage
✅ Complete	10	15%
🟢 Active Ready	12	18%
🟡 In Progress	35	52%
🔴 Critical	1	2%
🟠 Blocked	3	4%
🔵 Planning	4	6%
🔄 Transitioning	2	3%

Priority Actions

TODAY (2026-08-21):

• CRITICAL: test-coverage-implementation (24% done, blocks release, phases 3-6 pending)
• HIGH: label-prefix-enforcement-2026-08-05 (Phase 1 pending approval)
• HIGH: github-actions-v7-upgrade-2026-08-09 (needs implementation plan)

THIS WEEK:

• Complete Phase 5.2 validation (issue-maintenance-phase-5-2-staging)
• Finalize Phase 5.3 production readiness (issue-maintenance-phase-5-3-production-readiness)
• Verify Phase 1 completion for branch-naming-enforcement (targeted 2026-08-12)
• Phase 4 completion for changelog-automation-hardening

UPCOMING:

• Launch phase 2 for 8+ projects awaiting start
• Complete remaining testing agent planning phases
• Execute repo-restructuring Phase 1 (folder moves)
• Production deployment of issue-maintenance-scripts Phase 5

Projects Ready for Archival

10 complete projects can be moved to completed/ folder with archive documentation.

Changelog

Changed

• Updated active projects index with comprehensive status review for all 67 initiatives (2026-08-21)
• Reorganized active/README.md to categorize projects by status and completion percentage
• Added priority action items and maintenance checklist for ongoing project management
• Updated version numbers for both README files to reflect 2026-08-21 status snapshot

---

Checklist (Global DoD / PR)

• All AC met and demonstrated
• Tests not applicable (documentation update)
• Accessibility checklist completed (documentation only, N/A)
• Docs/readme/changelog updated (this is the update)
• Security checklist completed (documentation, no security implications)
• Code/design reviews approved (documentation update)
• CI green; linked issues closed; release notes prepared

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 27 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: d297ef05-bfca-403e-9dd9-842712558974

📥 Commits

Reviewing files that changed from the base of the PR and between c18e56f and 8bf3dd7.

📒 Files selected for processing (2)

• .github/projects/README.md
• .github/projects/active/README.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]

✅ Template check passed after update. Thanks for fixing the PR description.

[github-actions]

❌ Branch Name Validation Failed

The branch name chore/active-projects-status-update-ybw6ft 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.