Repository navigation
fix(get_neighbors): omitted depth honors the schema default (0 = immediate) - #244
Merged
Merged
Conversation
…immediate) Bug_DepthDefaultMismatch_2026_08_23: three depth numberings coexist — C hop-count (1 = immediate), MCP schema 0-indexed (default 0), op_bench d0. The TS boundary bridges with depth+1, but the handler defaulted omitted depth to 1 (and getNeighbors' signature to 1), so schema-default calls silently returned TWO-hop neighborhoods. Canonical semantics: the 0-indexed schema numbering. C hop-count is internal; the single +1 translation lives at the TS boundary. New test pins the OMITTED-depth path specifically — explicit-depth tests cannot catch a default divergence. Behavioral change: default get_neighbors walks shrink from 2-hop to the schema-promised 1-hop set. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017GGvxNSpbpc5TVyMYYYzBr
This was referenced Oct 8, 2026
Merged
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
1 participant
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.
Fixes the depth-default mismatch (found 2026-08-23): the tool schema advertised
default: 0but the handler resolved omitted depth as?? 1, so a call withoutdepthsilently returned two-hop nodes as "neighbors".+1at the TS->C boundary🤖 Generated with Claude Code