Use Bifrost declaration navigation#69
Merged
Merged
Conversation
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.
UsageBench still treated Bifrost declaration navigation as unsupported after Bifrost added the distinct
get_declarations_by_locationMCP tool. This updates the adapter to exercise the current declaration contract and score its exact locations.Key Changes:
get_declarations_by_locationwhile preserving the existing definition and profile-default paths.no_declarationresponses, advertise native declaration lookup capability, and retain machine-readable unknown-tool failures.Touch Points:
src/runners/bifrost.rsValidation:
cargo fmt -- --checkcargo test— 93 library tests, 2 CLI tests, and doctests passed using a consistent Rust 1.97.1 toolchain.cargo run -- validate benchmarks/cases— 35 case documents validated.9620eb8f: 132 passed, 13 failed, 3 expected failures, 2 unsupported, 0 position-unverified, and 0 runner errors. Eighteen declaration cases moved from unsupported to passed.