For QA leads who send a weekly quality update to managers or the team.

Your setup

Certyn runs suites or explore runs on your environments, and maybe your CI pushes its own results.
Issues have severities (critical, major, minor, trivial).
You want numbers and charts you can paste into an email or a meeting deck.

Say this to Certyn

Make this week's QA report for my manager: pass rate, trend by day, open bugs by severity, with charts.

Counts the last 7 days of results from runs (app.query on executions): passed, failed and blocked, per day, and per suite or version when useful. Pass rate is passed out of passed plus failed; blocked is shown on its own.
Reads the daily environment summaries and the versions deployed this week (app.metrics types daily and versions).
Groups open issues by severity, and counts issues found and closed this week (app.query on issues).
Reads the week's agenda: what was planned, what ran, and the wrap-up when the week is over (app.agenda.get).
Writes the report in the web chat: a short summary first, then charts (a line for pass rate per day, bars for open bugs by severity), then risks and next steps. Each issue and run is linked.

One report in the chat, with charts and numbers you can check through the links.
Text you can copy into an email, Slack or a slide.

There is no weekly email. The morning email comes every day at 08:00 in your time zone. You can set its question to "QA summary of the last 7 days", but it still comes daily and has no charts. For a weekly report, ask in the chat each Monday.
Charts draw only in the web chat. In Slack, Jira, Linear, MCP clients and email you get the same numbers as text.
Numbers cover only what Certyn knows: Certyn runs and results your CI pushes. Tests run elsewhere are not counted.
A week with few runs gives a weak trend. Ask Certyn to show the run count next to each number.