mirror of
https://github.com/DeusData/codebase-memory-mcp.git
synced 2026-11-11 09:25:35 +08:00
/api/impact answers the strongest-demand developer question in the information-needs literature: if I change this, what breaks and what must I retest. A reverse CALLS adjacency joins the flow cache (built in the same edge pass); a distance-labelled BFS from any symbol reports reachers per hop, a region rollup, and — separately — the test functions that reach the symbol, nearest first: the tests to run. Honest caps (depth 10, 50k visits, both flagged) and a stated basis: static CALLS only, so every count is a floor. The symbol page grows an 'If you change this' card: headline sentence, cumulative hop tiers, region chips, run-these-first test list with an explicit warning when no test reaches the symbol, and the floor footnote. Question family F3 flips to answered (7/8/3); the blast-radius wiki entry now names its caps. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>