Open
Conversation
petergarud
reviewed
Dec 3, 2025
Squid5678
requested changes
Jan 19, 2026
src/rj_strategy/include/rj_strategy/coordinator/seeking_client.hpp
Outdated
Show resolved
Hide resolved
src/rj_strategy/include/rj_strategy/coordinator/seeking_coordinator.hpp
Outdated
Show resolved
Hide resolved
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Added Seeker coordinator to handle seekers and seeker points without requiring several robots to keep track of each other.
Single source of truth for current seeker points.
Associated / Resolved Issue
Resolves # or ClickUp card
Resolves Clickup Issue: 86b6ubv6c
Design Documents
Link
Steps to Test
Test Case 1
Expected result: Seekers go brrr and no weird Seeker requests and responses needed (except with the coordinator ofc)
Key Files to Review
Group 1
Group 2
Review Checklist
(Optional) Sub-issues (for drafts)
Note: if you find yourself breaking this PR into many smaller features, it may make sense to break up the PR into logical units based on these features.