> I'm not sure there's anything better than manually tracing hotpaths

Ok, and where code changes happen the most is not the same as which code is used the most, is not the same as which code is the most important, is not the same as which code occupies the most computational resources. Code hotpaths are not represented by repo metadata.

You’re right. What I’m working on is meant to complement that, especially early on. The goal isn’t to replace judgment or deep dives, but to surface patterns that can guide where to look: areas with a lot of churn, untouched files, contributors active in a specific part of the code, etc.

It’s still early, but I’d like to evolve it to make those insights more actionable, maybe even link recent PRs, show how files evolved, or highlight ownership boundaries. Feedback like yours helps shape that, so thanks again.