Board-ready risk register

Pull [CLIENT NAME]'s risk register from ControlMap and build an artifact with:
1. A 5x5 likelihood-by-impact grid with each risk plotted at its current score
2. The top 5 risks rewritten for a non-technical board: what could happen, the business impact, and what we're doing about it (linked action items)
3. Risks with an Accept treatment, listed separately
4. Decisions needed: high risks with no owner or no linked action items

Keep it to one screen and use only real ControlMap data.

How to work with the ControlMap API (ScalePad MCP):
- Find the client with GET /controlmap/v1/clients/health and use its tenant ID (for example "dundmif") in every request. Some clients have no UUID.
- Send the header Content-Type: application/json on every POST, PUT and PATCH, including searches.
- Use page_size of 50 or less and follow next_cursor. The "fields" parameter is ignored, so responses are large.
- Judge controls by "status", not the "compliant" flag. Objective lists include sub-objectives, so take totals from objective_summary.
- Use framework-level scores and labels. The overall score_label on client health can be wrong.
- Older policy sections may be URL-encoded twice: decode them and use the highest version of each section.
- If a call returns 502 or fails to connect, wait a few seconds and retry once. If it still fails, tell me exactly which data is missing.