integrations: graphify importer — draft inferred contracts from graph… - #81
Merged
Conversation
….json The brownfield entry point (issue #80): a standalone script that reads a graphify knowledge graph and emits skeleton contracts, all status: inferred. Signatures come from the Python source via ast (the graph has none); deps only from EXTRACTED calls/references/inherits/implements edges between selected units; test candidates as pytest node ids. Refuses existing contracts by default; validates every emission through parse_contract. Pure tooling — no new MCP tools or CLI commands, nothing under src/. Dogfood: graphify-out/graph.json is the repo's own extracted graph (--code-only, local tree-sitter); sales README gains the bootstrap walkthrough. Importer handles the released CLI's format (links key, leading-dot method labels, L1 file nodes), not just the v8 source's.
This was referenced Jul 26, 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
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.
….json
The brownfield entry point (issue #80): a standalone script that reads a graphify knowledge graph and emits skeleton contracts, all status: inferred. Signatures come from the Python source via ast (the graph has none); deps only from EXTRACTED calls/references/inherits/implements edges between selected units; test candidates as pytest node ids. Refuses existing contracts by default; validates every emission through parse_contract.
Pure tooling — no new MCP tools or CLI commands, nothing under src/. Dogfood: graphify-out/graph.json is the repo's own extracted graph (--code-only, local tree-sitter); sales README gains the bootstrap walkthrough. Importer handles the released CLI's format (links key, leading-dot method labels, L1 file nodes), not just the v8 source's.
What and why
Checklist
uv run pytestpasses (full suite).contract.pyorimplhash.py? The hash-stability tests(
tests/test_contract_hash.py,tests/test_implhash.py) still pass, andany change to what busts a hash is intentional.
uv run python bench/benchmark.pystill reports >5x.
was discussed in an issue first.
HashloomError); no stack traces over MCP.