fix(labeler): give each C-* label a single automation owner

[WomB0ComB0]

Summary

Fast-follow to #60. That PR squash-merged before this refinement could be pushed to its branch, so it lands here.

CodeRabbit flagged a two-owner conflict on the shared change-type labels: C-Documentation, C-Testing, and C-Chore were applied by both the path labeler (.github/labeler.yml) and the conventional-title labeler. Because the path labeler runs actions/labeler with sync-labels: true, a later synchronize event removes any label defined in labeler.yml whose globs no longer match the PR's files — clobbering a title-applied C-* label (actions/labeler does not distinguish who applied a configured label).

Fix — one automation owner per label family

• .github/labeler.yml — drop the C-Documentation / C-Testing / C-Chore path rules. The path labeler now owns only area/scope labels (A-*, pkg:*), which it applies exclusively, so sync-labels: true can never strip a change-type label another workflow set. Change-type classification is driven by the conventional title, which is the authoritative signal for the release-note categories in .github/release.yml.
• .github/workflows/conventional-title-labeler.yml — the title labeler is now the sole owner of the change-type C-* labels, so its convergence set covers all seven types (feat/fix/perf/docs/refactor/test/chore). On a retitle it removes the stale change-type label and adds the current one, with no path labeler racing it.

.github/labels.yml is unchanged and still defines every C-* label (used by the title labeler and by release.yml categories).

Test plan

• .github/labeler.yml and .github/workflows/conventional-title-labeler.yml parse cleanly (js-yaml); no literal tabs.
• Every label referenced by labeler.yml (now A-* / pkg:* only) and by release.yml is defined in labels.yml.
• After merge: retitle a test PR feat: -> fix: and confirm only the current C-* remains, and that a docs:-titled PR keeps C-Documentation across synchronize events.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 34 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ef1c2fa3-4fc3-4cb5-b0a8-ebf15e8a3f98

📥 Commits

Reviewing files that changed from the base of the PR and between 49ff761 and df23f72.

📒 Files selected for processing (2)

• .github/labeler.yml
• .github/workflows/conventional-title-labeler.yml

---

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.}