I guess my question then is why should someone care about these patterns that are explicitly not what's "important"?

You say things like

"can guide refactoring, onboarding"

and

"For some workflows (e.g. legacy cleanup, team handover, bug tracking), that context can be quite valuable."

But those are vague hand-wavy statements that don't explain themselves. I don't understand why it would be valuable for those tasks, and I could use some explanation of what concrete problem is solved by looking at these details.

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.

Ok, and code hotpaths are not represented by repo metadata.