ci(labels): add label sync workflow + labels catalog

[flyingrobots]

Summary

• Add .github/labels.yml and a non-destructive sync workflow
• Complements the auto labeler/backfill added in xtask branches

Follow-ups after merge

1. Run 'Label Sync' workflow (workflow_dispatch)
2. Run 'Labeler Backfill' workflow to tag existing unlabeled issues
3. Optionally adjust label colors/names to taste

[coderabbitai]

Warning

Rate limit exceeded

@flyingrobots has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 13 minutes and 1 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between be9e50c and 925e8d1.

📒 Files selected for processing (2)

• .github/labels.yml (1 hunks)
• scripts/mermaid/generate.mjs (3 hunks)

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Summary by CodeRabbit

• Chores
  • Established a comprehensive labeling system for issues and pull requests with standardized categories including type, area, priority, and status.
  • Implemented automated label synchronization to keep repository labels up-to-date.

Walkthrough

Introduces automated GitHub label management via a new .github/labels.yml configuration file defining categorized labels (type, area, priority, status, needs) and a corresponding .github/workflows/label-sync.yml GitHub Actions workflow that synchronizes these labels to the repository on pushes to the configuration file or manual trigger.

Changes

Cohort / File(s)	Summary
Label Definitions ​.github/labels.yml	Adds comprehensive label configuration with ~30 labels across categories: type (bug, enhancement, docs, spec/design, tooling, test), area (xtask, schemas, diagrams, ci, build, determinism, privacy, governance), priority (p0, p1, p2), status (blocked), needs (info, repro), plus good-first-issue and help-wanted. Each entry specifies name, color code, and description.
Label Sync Workflow ​.github/workflows/label-sync.yml	Introduces "Label Sync" GitHub Actions workflow triggered on pushes to .github/labels.yml and manual dispatch. Grants read contents and write issues permissions. Runs crazy-max/ghaction-github-labeler@v5 with yaml_file targeting .github/labels.yml and skip_delete enabled to prevent label removal.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

• Label naming consistency: Verify all label names follow project conventions, avoid reserved keywords, and maintain consistent casing/hyphenation patterns across categories
• Color accessibility: Audit hex color codes for sufficient contrast and colorblind-safe palette adherence
• Workflow permissions: Confirm write: issues scope is minimal and necessary; validate skip_delete: true won't mask missing labels
• Typo verification: Each label entry requires careful inspection for spelling/formatting; the repetitive structure invites oversights
• Action version pinning: ghaction-github-labeler@v5 should be verified against latest stable release and known breaking changes

Suggested labels

ci, tooling

Poem

🏷️ Labels march in neat rows,
Colors bright and descriptions flow,
Actions sync them to and fro,
GitHub chaos? No, no, no! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly and concisely describes the main changeset: adding label definitions and a sync workflow to CI configuration.
Description check	✅ Passed	The description is directly related to the changeset, explaining what was added (labels.yml and sync workflow) and providing context about follow-up actions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

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 and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b938941 and be9e50c.

📒 Files selected for processing (2)

• .github/labels.yml (1 hunks)
• .github/workflows/label-sync.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Schema validation (v1)
• GitHub Check: Link Check (xtask links)
• GitHub Check: audit
• GitHub Check: fmt

🔇 Additional comments (3)

.github/labels.yml (1)

1-66: YAML syntax is now properly corrected—past issue resolved.

All label names containing colons (e.g., type: bug, priority: p1, needs: repro) are correctly wrapped in double quotes. The file will parse without Psych::SyntaxError.

.github/workflows/label-sync.yml (2)

1-22: Workflow structure and integration with labels catalog is sound.

The trigger is appropriately scoped to .github/labels.yml changes (avoiding spurious runs), workflow_dispatch enables manual override, and skip_delete: true honors the non-destructive sync requirement from the PR objectives. The yaml_file reference is correct and aligned with the labels catalog.

---

9-11: The permissions are correct—no changes needed.

The original concern was unfounded. crazy-max/ghaction-github-labeler requires repository read on contents and write on issues for label synchronization, which is exactly what the workflow declares. The action's own documented example uses this exact permission set. No escalation to contents: write is required.

Likely an incorrect or invalid review comment.