See which customers a work item affects

**Objective:** Work out which customers are affected by Azure DevOps work item `{work-item-id}` by finding the Zendesk tickets that point at it.

**Step 1: Read the work item (azure-devops server)**

Call `azure-devops-get-work-item` with `id` set to `{work-item-id}`. Note title, type, state, priority and url. If nothing comes back, say so and stop.

Call `azure-devops-get-work-item-comment` with `work-item-id` set to `{work-item-id}`. Collect every Zendesk ticket number mentioned in the title, description or comments (for example "ZD 4512", "ticket #4512" or a zendesk.com link).

**Step 2: Read the tickets (zendesk server)**

For each ticket number, call `zendesk-get-ticket` with `ticket-id` set to that number. If none were mentioned, call `zendesk-get-ticket` with `subject.contains` set to a distinctive phrase from the work item title and treat any hits as "possible" matches.

**Step 3: Report**

Give the work item in one line. Then a table of tickets: ticket-id, subject, status, priority, requester-name, requester-email, organization-name, created-date. Finish with the count of distinct organizations affected and how many tickets are still open (status not solved or closed).

**Rules & Guidelines:**

* `azure-devops-*` tools belong to the azure-devops server and `zendesk-*` tools to the zendesk server. Both servers must be connected; if a tool is missing, say which server is not connected and stop.
* This prompt is read-only. Never call `zendesk-add-ticket`, `zendesk-update-ticket`, `zendesk-add-ticket-comment`, `zendesk-make-ticket-comment-private`, `zendesk-add-user`, `zendesk-update-user`, `zendesk-add-organization`, `zendesk-update-organization`, `zendesk-add-organization-member`, `zendesk-add-group`, `zendesk-update-group` or `zendesk-add-group-member`. Azure DevOps has no write tools here.
* Pass `max-records` set to `{max-records}` on every call (default 50 when empty).

**Validation:**

* If no Zendesk ticket is linked, report the work item as having no known customer impact and say how you searched.
* If a ticket number from the work item does not exist in Zendesk, list it as "not found" rather than dropping it.
* Do not infer a customer from a name alone; use the requester email and organization name as returned.