(MOT-4187) feat(iii-directory): pass registry tags through the discovery proxy - #587
(MOT-4187) feat(iii-directory): pass registry tags through the discovery proxy#587rohitg00 wants to merge 1 commit into
Conversation
…ery proxy The registry envelope serves a tags array sourced from each worker's iii.worker.yaml manifest (live: GET /w/harness returns ["agent","harness","loop","autonomous"]), but the proxy's typed Worker model silently dropped the field, so directory::registry::workers::list and ::info rows never carried it. Add the field (tolerant default, omitted when empty), include it in the worker-info description's field list, and update the README field lists.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 52 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
skill-check — worker0 verified, 48 skipped (no docs/).
Four for four. Nicely done. |
1 participant
Problem
Every worker's
iii.worker.yamlcan declare discoverytags, and the registry serves them on the worker envelope (live:GET /w/harnessreturns"tags": ["agent", "harness", "loop", "autonomous"]). The proxy's typedWorkermodel silently dropped the field on deserialization, sodirectory::registry::workers::listand::inforows never carried it and mesh agents could not see or filter by tags at all.Change
Add
tags: Vec<String>to theWorkermodel (tolerant#[serde(default)], omitted from responses when empty, so older registry deployments and tag-less workers serialize unchanged), thread it through the one struct-literal fallback site, and name the field in theworkers::infodescription and README field lists.Tests
cargo fmt --check,cargo clippy --all-targets --all-features -- -D warnings,cargo test --lib(261) pass. Field presence verified against the live registry envelope before and after: the wire serves tags, the proxy now forwards them.Refs MOT-4187