From #1077 (comment) :
A.1: transparent_auth_digest
In the case that the transaction contains transparent inputs, this is a BLAKE2b-256 hash of the field encoding of the TransparentSighashInfo value for each transparent input, followed by the field encoding of the Bitcoin scriptSig value for each transparent input: [...]
There is another ambiguity in this wording that we didn't spot in the ZIP sync: is input_sighash_infos given by BLAKE2b-256(concatenation of TransparentSighashInfos), or by the concatenation of BLAKE2b-256(TransparentSighashInfo)? I believe it's the former, but this wording could mean either.
From #1077 (comment) :