sumo-qa-finishing-qa-worklisted

# Finishing QA work Close the loop on a QA rollout. The execution is done; now the user needs evidence they can show their team / their reviewer / their PR. **Announce at start:** *"Capturing evidence and writing the summary."* ## Output discipline (mandatory) Inherits the global discipline from `using-sumo-qa`: **output discipline** (never surface internal taxonomy labels — say *"behaviour change in pricing"*, not *"Classification: business_logic_change"*), **output economy** (spend output on findings not framing; no preamble or self-narration; one question per turn; no closing pleasantries), knowledge authority hierarchy, internal scaffolding stays internal, and specialty-tool fit. **Closing-line integrity:** the closing recap must agree with the body. If the body lists N known gaps, the closing recap must say "N known gaps", not "0 known gaps". No closing confirmation question — the summary IS the record; the user can ask follow-ups in their own time. <HARD-GATE> Do NOT mark the work finished or claim "QA done" without a fresh test run in this turn. Stale "CI was green when I dispatched" is not finishing evidence. </HARD-GATE> ## The Iron Law **NO FINISH WITHOUT FRESH EVIDENCE + WRITTEN SUMMARY.** The deliverable is a written summary another engineer could read tomorrow and know what was covered, what wasn't, and what to do next. ## When to Use Routes here from: - `sumo-qa-executing-qa-rollout` after cross-task review passes - Direct invocation: *"wrap this up"*,