fix(sdk): derive placement repoKeys from repo:<key> node tags

[willwashburn]

messaging.placement.spawn({ repo }) filters candidate nodes with node.repoKeys?.includes(repo), but nothing in the stack produces a repoKeys/repo_keys/repoPaths field on the engine's node roster row — the only repo advertisement that flows end-to-end (fleet definition → provider registration → engine node row → roster) is repo:<key> tags. A repo-filtered placement therefore matched no node, ever.

toRelayNode now derives repoKeys from repo:<key> tags when no dedicated field is present. Explicit repoKeys/repo_keys/repoPaths still take precedence, so a future engine-side field slots in without SDK changes.

This makes repo-aware placement work for node definitions that tag their serviceable repos — e.g. the factory node (@agent-relay/factory/node), which advertises repo:<label> tags from its clone map.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in:33 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 00a742cd-5830-49ae-a6b6-b6d8a8e0eced

📥 Commits

Reviewing files that changed from the base of the PR and between 825f595 and fc66847.

📒 Files selected for processing (1)

• CHANGELOG.md

📝 Walkthrough

Walkthrough

Node translation derives repoKeys from repo: tags when explicit repository paths are unavailable. Tests cover tag-derived keys, explicit-field precedence, and missing repository metadata.

Changes

Repository key translation

Layer / File(s)	Summary
Repository key fallback and validation packages/sdk/src/messaging/relaycast-translate.ts, packages/sdk/src/__tests__/messaging.test.ts	readRepoKeys prioritizes explicit repository paths and otherwise extracts non-empty repo: tag values; tests verify fallback, precedence, and undefined results.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers:khaliqgant

Poem

I’m a bunny with keys in a tag,
repo: trails tucked in my bag.
Explicit paths lead the way,
Empty tags hop away.
Tests thump approval—yay!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description covers the summary, but it omits the required template sections and has no test plan or screenshots.	Add the template headings for Summary, Test Plan, and Screenshots, and fill in the test checklist items.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately captures the main change: deriving placement repoKeys from repo-tagged nodes.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch placement-repo-keys-from-tags

---

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

[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!

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:f3b967a85b

ℹ️ 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".

[chatgpt-codex-connector]

Add the SDK placement fix to the changelog

This change fixes @agent-relay/sdk repo-filtered placement behavior, so it is user-visible. The root AGENTS.md requires curating CHANGELOG.md under [Unreleased] as PRs land, but this commit leaves [Unreleased] empty; release notes for the next patch would omit this fix. Please add a concise Fixed entry under [Unreleased - Patch].

Useful? React with 👍 / 👎.