New requirement impact check

Here is a new or updated requirement:

[REQUIREMENT]

1. Summarize what it requires in plain language
2. Identify which ControlMap clients it likely applies to, based on their frameworks and what we know about them
3. Find existing controls that already cover it
4. List the new work: policies to update, controls to add, evidence to collect

End with a short client-facing note from [MSP NAME]. Read-only.

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.