Feature Request: Configure a separate commit hash for audit vs client repos

The Repository Configuration section currently accepts one commit hash and applies it to both repo urls, which sometimes doesn't make sense. For example, while auditing two client repos, one might use git modules or subtrees to make them both accessible in one audit repo. Or, maybe the audit repo has additional fuzz tests added to it. In either case, the commits are different and at least one of the resulting permalinks will be wrong.

Start by locating the Repository Configuration implementation and the code that applies the configured commit hash to repository URLs and generates permalinks. Trace how both repositories currently receive the hash; done means audit and client repositories can use separate commit hashes so each resulting permalink points to the correct commit.