Repository navigation
feat(mcp): optional edge_types allow-list for graph traversal, document edge types - #9
Merged
Merged
Conversation
…nt edge types focus_pack, impact_analysis and guided_path followed every outgoing edge regardless of its type; guided_path only printed the type. They now accept an optional edge_types allow-list. The default (None) keeps the current behaviour and the result shape; with a list the result echoes the types. An empty list follows no edge. kb_data/edge_types.md was stale (2 of the 4 types the graph builder emits). generate_edge_types_doc now states what each type means, so readers do not treat embedding similarity, chunk order, explicit references and the call graph as equivalent. Per-build counts are left out on purpose: the file is tracked. Refs #8 --- [signing-metadata] key = cic-my-sign-key signature = vault:v1:MEQCIFv6Tl9vbrUa36oH7C5+g8vMkEi3qkG1zicMfG//zVvVAiB0Zf3lngLgqEyfNIcwYKtHhITEsdhckwcvjKUPh3qoPw== hash-algorithm = sha256 digest = /jHKTVOJ3X0tZBpYsvCUjWgkahs2etF+ULnDgE3+Lv4= [certificate] -----BEGIN CERTIFICATE----- MIICBjCCAaygAwIBAgIUSnRMR6RPnEbg296XWPOqq/u5PCwwCgYIKoZIzj0EAwIw QzELMAkGA1UEBhMCSFUxGTAXBgNVBAoMEENlbnRyYWxJbmZyYUNvcmUxGTAXBgNV BAMMEENJQyBEZXZlbG9wZXIgQ0EwHhcNMjYwMzIwMTMyMjU5WhcNMjYxMjMxMTMy MjU5WjBFMQswCQYDVQQGEwJIVTEZMBcGA1UECgwQQ2VudHJhbEluZnJhQ29yZTEb MBkGA1UEAwwSR2Fib3IgWm9sdGFuIFNpbmtvMFkwEwYHKoZIzj0CAQYIKoZIzj0D AQcDQgAEIG2CVmTfmLB9pLLclj7YmP2eedAjklpy4LGrU2ijoiy6Xqpuybv7OgJe i+ez31s65NEV8+X/ByeX1cstR988z6N8MHowCQYDVR0TBAIwADAdBgNVHQ4EFgQU yZN6AIX/TNnIJ9GwAa/NRN3ujHAwHwYDVR0jBBgwFoAUXn6CHYzPUqU4JVP8g+OS WeDYjhcwDgYDVR0PAQH/BAQDAgeAMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEF BQcDBDAKBggqhkjOPQQDAgNIADBFAiEA+bFzXRoJ4PCQbhAAtpkcMjt0vNj5rEW0 lOMBGDNyaWkCIB1vmM7PcZzv/c9bIrxF5kqv6QXomouhByUfeNUTbpKW -----END CERTIFICATE-----
5 tasks
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.
Refs #8.
What
What this does not do
No traversal default is changed. The experiments in #8 found no quality effect of untyped traversal (precision identical across variants with a working judge), so only the verified, behaviour-neutral items are fixed.
Verified locally
Known, not touched
The companion YAMLs `server.yaml` / `make_source.yaml` had already drifted from the code (e.g. `load_kb`, `process_py_yaml`); a full `py.meta.gen --merge` would pull that into this PR, so it is left for a separate change.
🤖 Generated with Claude Code