Conversation
winners and phases in challenge details tool -> dev
PM-6003 - project search fix
kkartunov
approved these changes
Sep 15, 2026
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.
This pull request enhances the challenge search agent and project/challenge toolchain to better handle project name resolution, enrich challenge details with winners and phase data, and improve linking to member profiles in generated responses. The changes include updates to both agent instructions and tool interfaces, as well as new and expanded tests to ensure correct behavior.
Project and Challenge Resolution Improvements:
fetch-project-by-idtool now accepts either a numeric project id or a project name. When a name is provided, it searches for projects by name, preferring exact matches and surfacing ambiguous results for user disambiguation. The tool's output now includes how the project was resolved and any additional matches. [1] [2] [3]challenge-vector-query-toolinput schema now documents that only numeric ids are valid forprojectId, and names must be resolved first.Challenge Details Enrichment:
fetch-challenge-by-idtool and its schema now returnwinners(with handle, userId, and placement) andphases(with detailed timing and status info) when present. [1] [2]Response Formatting and Linking:
MEMBER_PROFILE_BASE_URL, with instructions on formatting and ordering (by placement) these links in markdown. [1] [2]Testing Enhancements:
Project and Name Resolution:
fetch-project-by-idtool to accept both numeric ids and project names, performing name search with disambiguation and surfacing ambiguous matches. Output now includes resolution method and extra matches. [1] [2]Challenge Details and Enrichment:
winnersandphasesfields to thefetch-challenge-by-idtool, including schema changes and data mapping. [1] [2]winnersandphasesfields.Agent Instructions and Output Formatting:
Schema and Documentation Updates:
challenge-vector-query-toolinput, clarifying that only numeric ids are valid forprojectId.