Client welcome pack

Build a welcome pack artifact for [CLIENT NAME]'s compliance program with [MSP NAME], using their ControlMap setup.

Include:
- What [FRAMEWORK] is and why it matters to their business, in two sentences
- The phases ahead and roughly when each happens
- What we need from them, and who on their side is involved
- What they'll receive from us (reports, reviews, trust page)
- How to reach us

Warm and plain-language, no control IDs. Use only real ControlMap data for dates and scope.

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.