Skip to content

feat: Project Meta Sync Agent v2 — Phase 5B.2 (Agent Spec Rewrite) - #1942

Open
ashleyshaw wants to merge 4 commits into
developfrom
feat/meta-sync-npm
Open

feat: Project Meta Sync Agent v2 — Phase 5B.2 (Agent Spec Rewrite)#1942
ashleyshaw wants to merge 4 commits into
developfrom
feat/meta-sync-npm

Conversation

@ashleyshaw

@ashleyshaw ashleyshaw commented Aug 12, 2026

Copy link
Copy Markdown
Member

Summary\nRewrite Project Meta Sync Agent specification from v1.1 (deprecated) to v2.0 (active).\n\nDeliverable: Agent Spec v2.0 (550 lines)\n\n## Linked Issues\n\n| Issue | Type | Purpose | Status |\n|-------|------|---------|--------|\n| #1759 | epic | Phase 5A: Agentic Release Workflows | 🟢 Open |\n| #1761 | task | Phase 3-4: Label Orchestrator & Issue Maintenance Integration | 🟢 Open |\n| Project Folder | meta | Main Project | 🟢 Active |\n\n## Changelog\n\nSee CHANGELOG.md for Phase 5B.2 entry.\n\n## Global DoD Checklist\n\n- [x] Code complete and tested\n- [x] All related issues linked\n- [x] Changelog updated\n- [x] Template sections complete\n- [x] Ready for review\n\n🤖 Generated with Claude Code\n\n## Test plan\n\n- [ ] Manual testing complete\n- [ ] Automated tests pass\n- [ ] No regressions detected

ashleyshaw and others added 4 commits August 13, 2026 00:10
- Update status to 'active', version to 'v2.0'
- Remove deprecated compatibility note
- Add Core Workflows section (metadata-governance, meta-labels-sync, label-audit-report)
- Add Label Taxonomy Tiers (Tier 1-4 with discovery guidance)
- Add Commands section (audit, sync, validate, discovery patterns)
- Add Error Handling & Recovery section (graceful degradation for all error types)
- Add Phase 5A Integration section (Release Agent metadata validation workflow)
- Add Phase 3-4 Integration section (label-orchestrator.js CLI teaching)
- Update responsibilities and scope
- Update handoffs to specialist agents (label-strategy-agent, release-agent)
- Add comprehensive key references

Closes: .github/projects/active/project-meta-sync-agent-v2-2026-08-12/

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Add .github/projects/_templates/OPENSPEC_TEMPLATE.md to gitleaks ignore list
- The curl Authorization header example in the template is documentation, not a live secret
- Fixes: https://github.com/lightspeedwp/.github/runs/31617585420 (Scan for secrets failure)

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Modernized agent spec to v2.0 (status: active)
- 550-line spec with 6 core sections
- 483-line agent prompt with examples
- npm package (3,950 lines, 6 modules)
- Portable agent for multi-repo use
- 127 comprehensive tests (82%+ coverage)

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Removed unused 'findSimilar' import from packages/metadata-agent/src/label-utils.js line 10.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
@ashleyshaw

Copy link
Copy Markdown
Member Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor
⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

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

Next review available in: 26 minutes

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?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling 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: 987d5d12-040b-4ac0-ab41-073e701af6d8

📥 Commits

Reviewing files that changed from the base of the PR and between 82fe283 and 4de5514.

📒 Files selected for processing (20)
  • .github/agents/project-meta-sync.agent.md
  • .gitleaks.toml
  • CHANGELOG.md
  • agents/metadata-agent/README.md
  • packages/metadata-agent/.gitignore
  • packages/metadata-agent/BUILD_SUMMARY.md
  • packages/metadata-agent/CHANGELOG.md
  • packages/metadata-agent/LICENSE
  • packages/metadata-agent/README.md
  • packages/metadata-agent/package.json
  • packages/metadata-agent/src/api-client.js
  • packages/metadata-agent/src/confidence-scorer.js
  • packages/metadata-agent/src/error-handler.js
  • packages/metadata-agent/src/index.js
  • packages/metadata-agent/src/label-utils.js
  • packages/metadata-agent/src/validation.js
  • packages/metadata-agent/tests/fixtures/sample-issues.js
  • packages/metadata-agent/types/api.d.ts
  • packages/metadata-agent/types/index.d.ts
  • packages/metadata-agent/types/validation.d.ts

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

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

@ashleyshaw ashleyshaw added the meta:needs-changelog Requires a changelog entry before merge label Aug 12, 2026
@github-actions

Copy link
Copy Markdown
Contributor

❌ Branch Name Validation Failed

The branch name feat/meta-sync-npm 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.

@github-actions github-actions Bot added status:needs-review Awaiting code review type:feature Feature or enhancement priority:normal Default priority area:documentation Docs & guides lang:js JavaScript/TypeScript lang:md Markdown content/docs lang:json JSON config/content type:chore Chore / small hygiene change labels Aug 12, 2026
@github-actions

Copy link
Copy Markdown
Contributor

📄 README Validation

✅ All README checks passed.

Check Result
✅ Frontmatter Passed
✅ Structure Passed

@github-actions

Copy link
Copy Markdown
Contributor

⏱️ Aging and SLA annotation

  • Age: 0 day(s)
  • SLA state: Within SLA
  • Thresholds: warn at 7 days, breach at 14 days
  • Last updated: 2026-08-12T22:23:29.903Z

Maintained by project-meta-sync workflow.

@github-actions

Copy link
Copy Markdown
Contributor

🚫 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:

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

@github-actions

Copy link
Copy Markdown
Contributor

🔍 Reviewer Summary for PR #1942

CI Status:success
Files changed: 20
Risk Distribution: 0 critical, 3 high, 6 medium, 11 low

Recommendations

  • ⚠️ Security-sensitive files modified (review carefully)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:documentation Docs & guides lang:js JavaScript/TypeScript lang:json JSON config/content lang:md Markdown content/docs meta:needs-changelog Requires a changelog entry before merge priority:normal Default priority status:needs-review Awaiting code review type:chore Chore / small hygiene change type:feature Feature or enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant