Context:

Instead of tracking code coverage/browser test health in a RelEng KPI 9and thus implicitly say we are primarily responsible for making those numbers better), it was suggested to make a scoreboard that tracks this information that will encourage all developers to make improvements.

There's an existing code coverage report and efforts to expand it T71685: Generate PHP code coverage reports for extensions.