Add "resolved-command" ?

[yarikoptic]

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.

[asmacdo]

IIUC idea is, prior to execution, we execute a different command and record the results into info.json?

In my view it would we would really want to be able to execute multiple commands, and place each into its own custom field, ie which datalad -> datalad_path

Also seems useful for recording versions of things

I imagine we would want to add a top level field to namespace extra fields in the file. Heres a few GPT suggestions I liked

extensions: Suggests that this part of the dict is for custom or additional fields beyond the main structure.
custom_fields: Clearly indicates that the fields are not part of the original set.
metadata: Commonly used for supplementary or additional data.
extras: Implies added, non-essential data.
annotations (my vote): If the fields are more about adding descriptive or auxiliary information.
supplemental_data: For extra data that enhances the existing information.

[asmacdo]

related #31