feat: add brick_callers and brick_uncalled caller-status queries #4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/caller-status"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Stacked on #3 (
feat/cpp-rust-resolution); review and merge that first. This adds agent-facing MCP queries that answer "is this function used?" without ever turning an unresolved call graph into a dead-code verdict.brick_callers {node_id, assume_closed_world?}returns one of three statuses:resolved, with the complete caller edges;unknown, with the reasons callers may exist;unreferenced.It also returns an evidence
basis(heuristicorcompiler), the language'smetrics.resolutioncoverage, and a fixed caveat.brick_uncalled {language?, assume_closed_world?, include_unknown?, limit?}returns per-language status counts and a deterministic list of review candidates.Reasons for
unknown:#[test],#[tool], …);assume_closed_worldis set.Also adds the research write-up (
docs/research/cpp-rust-resolution.md): the audit, the literature found through paperbridge, the experiment contract, results, and limits.Validation on YAMS (dead-code candidates checked with grep)
Test plan
cargo test(103 tests), clippy and fmt pass.tests/callers.rscovers each reason with positives and clean negatives.mcp_runner.pyself-test/run pass with the two new tools../scripts/quality-gate.shpasses.🤖 Generated with Claude Code