sumo-qa-measuring-coveragelisted

# Measuring coverage & mutation Turn a repo's coverage/mutation run into evidence the QA report can cite. The report reads `.sumo-qa/coverage.json` and `.sumo-qa/mutation.json`; this skill produces them. The host (you) runs the tool and reads its output; the MCP tools only validate + persist. **Announce at start:** *"Measuring coverage/mutation and recording it for the report."* ## Output discipline (mandatory) Inherits the global discipline from `using-sumo-qa`: never surface internal taxonomy labels; spend output on findings not framing; one question per turn; no preamble or closing pleasantries. <HARD-GATE> NEVER fabricate a number. A coverage percentage or survivor count goes into an artifact ONLY when it came from a real run (or a report the user pointed you at) in this session. No run / no report ⇒ record nothing, report "not available". </HARD-GATE> ## The Iron Law **MEASURED, REPORTED, NEVER GATED.** Coverage and mutation are evidence the report *shows* — they never become a pass/fail gate and never flip a readiness verdict. A 100% coverage signal does not make a risk "covered" or a blocked verdict "ready". If you catch yourself treating a percentage as a safety threshold, stop. ## When to Use - *"run coverage and put it in the report"*, *"measure coverage"*, *"what's my coverage"* (when the report should carry it) - *"run mutation testing"*, *"record the survivors"*, *"get mutation into the scorecard"* - As a follow-on to a QA rollout, before `sumo_qa_genera