Add "resolved-command" ?

not yet even sure it would help in my case. I wanted to record which actual `git-annex` (I have many installed and adjust PATH to use specific one) is used via testing which command was actually executed -- likely we would need to traverse `$PATH` "manually" for that. But it would not even help since I would determine `git` but it would not necessarily be overloaded along with git-annex. So it would require ad-hoc handling to determine actual git command and see if it is annex... not yet sure if worth the complexity.

The issue does not identify any files, tests, or entry points to inspect. First clarify whether a resolved-command feature is needed and how it should distinguish the selected git-annex and git executables under PATH; done would require an agreed scope and behavior before implementation can be assessed.

Written by the indexing model from the issue text.