fix: preserve edge confidence in call trace results - #336
Conversation
🌱 graft blast radius1 area changed → 4 areas can be affected. 8 dependent symbols, depth 2. flowchart TB
A0(("Tool Invocation<br/>3 symbols"))
A1(("Blast Radius<br/>2 symbols"))
A2(("Workspace Federation<br/>2 symbols"))
A3(("CLI Entry Point<br/>1 symbol"))
classDef reached fill:#D9EDF3,stroke:#3AA7C9,stroke-width:1.5px,color:#0E313C;
class A0,A1,A2,A3 reached;
Who knows this code — 2 people across 5 areas
Ownership is git history over each area's own files, weighted towards recent work (120-day half-life). Merge commits and bots are dropped, and you are dropped from your own PR. A name with no All 8 dependent symbols, grouped by areaTool Invocation — 3 symbols in 1 file
Blast Radius — 2 symbols in 1 file
Workspace Federation — 2 symbols in 2 files
CLI Entry Point — 1 symbol in 1 file
Test signal per changed area — 1 ✓Reached = a node under a test path has a resolved edge into the changed symbol. It undercounts anything called indirectly — through a CLI, a spawned process or a dynamic import — so read a low ratio as “look here”, never as a coverage gate.
4 test suites also reference this code4 symbols, kept out of the diagram and the table so they cannot crowd out the areas a reviewer has to look at.
Open the interactive graph → — click an area to see its dependent symbols at file:line. |
Preserve confidence in call trace results (point 4 of #330), complementing #335's import-resolution fix.
Traversal order, deduplication, depth, and resolution remain unchanged.
Validation: