I have a concern: this does not find the most obvious reference - where the cursor is. And all other references in doc comments.

My main use case for the current impl is to look up code whilst keeping the view of the documentation in the current editor, and did not expect the documentation links to appear there.

Also, I suspect that if we start showing all docs' references, that will make the reference lookup even slower and bloated with results?

So, personally, I'd love to keep things as they are, as I am rarely interested in docs' usages, but very interested in the real code related.

I do not know internals good enough, but suspect that if we want to track those references in docs as proposed, we need to go over almost all the "stack" starting with lowering?
I'm not sure I will be able to do that, and neither I am interested right now: I want to make completions to work inside doc comments and this was a practice PR before that.

I have a concern: this does not find the most obvious reference - where the cursor is. And all other references in doc comments.

This would be ideal behavior, but shouldn't block this PR. Its an improvement over the current state after all.