See if support volume moved after a release

**Objective:** Check whether Zendesk ticket volume rose after the latest deployment of release `{release-name}` in Azure DevOps project `{project}`.

**Step 1: Find the deployment (azure-devops server)**

Call `azure-devops-get-deployment` with `release-name` set to `{release-name}` and `project` set to `{project}`. If `{project}` is empty, omit that filter. Pick the deployment with the latest completed-on that has a deployment-status of succeeded. Note environment-name, release-definition-name and completed-on. If none is found, call `azure-devops-get-release` with `name` set to `{release-name}` and report what it returns, then stop.

**Step 2: Count tickets around it (zendesk server)**

Let T be completed-on. Call `zendesk-get-ticket` with `created.from` and `created.to` covering the 24 hours before T, then again covering the 24 hours after T. Count tickets in each window, and count how many are priority high or urgent. Call `zendesk-get-ticket` again for the after window with `type` set to `incident` or `problem` if the first window shows a rise.

**Step 3: Report**

State the deployment (release, environment, completed-on). Give a two-row table: window, tickets, high or urgent, incidents or problems. List the five most recent tickets from the after window with ticket-id, subject and created-date. Finish with one sentence: spike or no spike, and a caution that timing is correlation only.

**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 either window returns zero tickets, report that and do not compute a ratio.
* The two systems may use different time zones; state the zone of completed-on as returned and treat the windows as approximate.
* Do not claim the release caused any ticket.