What can we do to deliver code-coverage metrics via this (or another) testing framework?

To raise customer confidence in our libraries, and to give us confidence in our ability to refactor them, it would be valuable if we could have available to us metrics and visibility about the code coverage of our tests. Is there a path available to us to provide that data?

Start by inspecting the repository's existing Go test setup and identifying how tests are run. Compare feasible ways to collect and expose code-coverage metrics, then define a reproducible workflow and document what coverage data is produced and how it can be viewed.

Written by the indexing model from the issue text.