Risk Mapping: What landed where in a system map

A while ago I made a system map - how everything interconnects together in order to give a good visual of a complex system, very useful for general consumption but I wondered lately if I could turn that itself into its own heat map, in order to focus testing in the risky areas and catch any potential sneaky problems in areas that relate, which aren't obvious. 

I wanted this view but I want to send it a body of work that makes up a release, then light up those areas that had changed:

Clicking on any of the nodes lists out what it is and links all of the associated stories and pull requests.

In order to generate this I run a python script Claude helped to generate, I give it a PAT token so it can talk to Azure DevOps and I simply feed in a query that contains all the work merged for release X, Y or Z which gets fed back per node along with its parent story. I hope this will help stop us regression testing areas that don't need the attention and focus the attention where it matters.