I love the semantics of the UI here; helping humans wade through what the code _means_ as well as what it is doing. "These tests/prod methods/data models/etc a

I love the semantics of the UI here; helping humans wade through what the code _means_ as well as what it is doing. "These tests/prod methods/data models/etc are impacted" really matters to me because that's most likely what I'm trying to do when I'm grepping for `verified` and adding a bunch of path constraints `!model !test`, etc. Leveraging that further for automations like "run all impacted tests" is another game changer for many companies. Can this help me draw flowcharts and the like? I recently did a bit of a refactor and "show me the stack of calls from the API layer leading to method m" was a lot more work than it should have been!