ci(labeler): route packages/core changes to the harness label

[Astro-Han]

Summary

packages/core/** had no rule in .github/labeler.yml, so any PR touching only packages/core could not satisfy the label policy: pr-triage runs actions/labeler with sync-labels: true (which strips any routing label not backed by a path glob), and .github/scripts/label-policy-check.js then requires at least one routing label (app/ui/platform/harness/ci). The result was a structural deadlock — the labeler removed any manually added routing label, and pr-triage failed every time.

Map packages/core/** to harness, alongside the existing packages/opencode/** and packages/sdk/** rules (core is the engine the opencode harness builds on).

Why

Without this, every packages/core-only PR is un-mergeable under the label policy. This surfaced on #1167 (a core/util/log.ts fix). The fix is one glob and unblocks all future core-only PRs.

Related Issue

None — discovered while landing #1167.

Human Review Status

Pending

Review Focus

That harness is the right routing bucket for packages/core (it backs the opencode CLI/runtime, not the desktop app/ui/electron/ci surfaces).

Risk Notes

Minimal. CI label-routing config only; no product code, no build/test behavior. Worst case is a mis-routed label, fixable by editing one line.

How To Verify

After merge, re-trigger pr-triage on a packages/core-only PR (e.g. #1167):
the labeler assigns `harness` from the new packages/core/** glob, and the label
policy (one type + one priority + one routing) passes.

Screenshots or Recordings

N/A — CI config only.

Checklist

• Type label — exactly one of bug, enhancement, task, documentation (task).
• Routing labels — ci is auto-assigned by the labeler (this PR touches .github/**).
• Priority label — auto-suggested by the triage bot.
• Human Review Status: Pending.
• I linked the related issue, or stated in Summary why there is no issue.
• I described the review focus and any meaningful risks.
• I replaced the example block in How To Verify with the real verification steps.
• I did not introduce unrelated changes beyond the stated scope.
• I reviewed the final diff.
• I am targeting dev, and my PR title and commit messages use Conventional Commits in English.

Summary by CodeRabbit

• Chores
  • Updated GitHub workflow configuration to optimize labeling processes.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 5cc7b991-7760-46a6-9721-62c23c4297fc

📥 Commits

Reviewing files that changed from the base of the PR and between 83204d7 and 88157e3.

📒 Files selected for processing (1)

• .github/labeler.yml

---

📝 Walkthrough

Walkthrough

Updated .github/labeler.yml to extend the harness labeler to automatically apply to changes within packages/core/** file paths.

Changes

Harness Labeler Scope

Layer / File(s)	Summary
Harness labeler scope update .github/labeler.yml	Added packages/core/** to the harness labeler's changed-files criteria.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Astro-Han/pawwork#573: Related .github/labeler.yml changes that define and extend path-based label routing rules for the harness scope.

Suggested labels

ci, harness

Poem

🐰 With whiskers twitching, I organize with glee,
packages/core/** now labeled perfectly!
The harness scope expands, no paths left behind,
Configuration magic, so tidy and refined. 🏷️

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and specifically describes the main change: adding packages/core to the harness label routing in the GitHub labeler configuration.
Description check	✅ Passed	The description is comprehensive and covers all required template sections: Summary, Why, Related Issue, Human Review Status, Review Focus, Risk Notes, How To Verify, and a substantially completed Checklist.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/labeler-core-routing

---

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

[github-actions]

Suggested priority: P2 (includes non-doc, non-test paths outside the low-risk bucket).

P1/P0 are reserved for maintainer confirmation. Please relabel manually if this is a release blocker, security issue, data-loss risk, or updater/runtime failure.