sumo_qa_generate_qa_report
Compile persisted QA artifacts into a local QA report, returning a compact readiness summary. Optionally write the self-contained HTML page to disk.
Instructions
Compose the persisted .sumo-qa artifacts (repo map, diff
impact, risk ledger, context bundle) into the local QA report and
return a compact readiness summary. The
rendered HTML body never rides back to the host — pass write_to to
persist the self-contained static page and open it from disk.
Common natural-language phrasings that map to this tool: "generate the QA report", "build the QA dashboard for this repo", "give me the local QA readiness report", "render qa-report.html".
root is the repository to report on (absolute or relative to the
MCP server's working directory). Every artifact is OPTIONAL: a missing,
invalid, or stale source renders an explicit honest state. The readiness
verdict (ready / ready_with_accepted_residuals / blocked /
insufficient_evidence) is derived by the QaScorecard readiness engine
from the risk ledger + context bundle — missing data is never reported
as passing evidence.
risk_ledger_rows / context_bundle are inline overrides for the
chat flow where the ledger/bundle was built in-conversation and never
persisted (the same shapes sumo_qa_format_risk_ledger /
sumo_qa_format_context_bundle accept). They take precedence over
any on-disk file and are validated BEFORE anything is written.
write_to is optional — when set, the page is written there
(relative paths land under the target repo; the conventional value is
.sumo-qa/qa-report.html). Without it the tool writes nothing.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| root | Yes | ||
| write_to | No | ||
| context_bundle | No | ||
| risk_ledger_rows | No |