Compliance section for the QBR

Build the compliance section of [CLIENT NAME]'s QBR as a short slide deck.

From ControlMap: framework progress since last quarter, closed and open gaps, top risks.
From Lifecycle Manager: initiatives and budget related to those gaps.

Slides:
1. Where you stand, one number per framework with trend
2. What we accomplished this quarter
3. The three risks that matter most, in business terms
4. Next steps, each tied to a Lifecycle Manager initiative and cost (flag gaps with no initiative yet)

Plain language, prepared by [MSP NAME].

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.