Enrich DiffGraph is usable information

[avikalpg]

Currently, looking at the diffgraph, I am not able to make a lot of sense of the code blocks as well as the changes that are happening in it.
Here are some changes that can be made in order to improve that:

• ensure that the dependency edges are shown in the order in which they are called.
• the hover block doesn't just contain a summary of the change, but has expandable sections talking about "what did the code block do?", "what has changed in it?" and the actual diff specifically of that code block.
• each block should have some indicators that can help the developer. Things like scores for "cognitive complexity", "size of change" as +2-11, and other linting issues; along with a logo indicating the type of code block (function, class, trait, script, configuration, end-point etc.)
• clicking on the nodes/edges should open that part of the code in the editor

[nia-sg-bot]

Product-direction review — 2026-08-01

Verdict: REVISE · P1

Keep the user outcome, but split it into evidence-backed schema data, renderer interactions, and VS Code navigation. “Called order” must mean source call-site order—not claimed runtime order. Metrics/lint need tool/version/config provenance. Optional AI may explain verified findings; it cannot create relationships or metrics.

This is a scope/alignment review, not an automatic closure decision. Items marked DISCUSS CLOSE should be resolved with maintainer context before closing.