Give customers an accurate update on escalated Zendesk tickets

**Objective:** For Zendesk ticket {ticket-id}, find the linked Jira issue or issues, report their progress, and draft (but do not send) an update for the customer.

**Step 1: Read the ticket (Zendesk)**

Call `zendesk-get-ticket` with ticket-id {ticket-id}. If nothing comes back, stop and say so.

**Step 2: Find the linked Jira issues**

Call `zendesk-get-ticket-comment` with ticket-id {ticket-id} and public false and collect every key from notes starting `Linked Jira issue:`. Then call `jira-get-issue` with summary.contains `[ZD-{ticket-id}]`. Merge both sets. If neither finds anything, report that the ticket has not been escalated to Jira and stop.

**Step 3: Read each issue (Jira)**

For each key, call `jira-get-issue` with issue-key to get status, assignee, due date and last update. Call `jira-get-issue-comment` for the issue and keep the three most recent comments.

**Step 4: Report**

* Ticket: id, subject, Zendesk status, requester, organization.
* One row per Jira issue: key, status, assignee, due date, last updated, and a one-line summary of the latest comment.
* A flag if the ticket is solved or closed while an issue is still open, or the reverse.
* A draft customer reply of 2 to 4 sentences, in plain language, with no internal names, Jira keys or estimates the Jira comments do not support.

**Rules & Guidelines:**

* `zendesk-get-ticket` and `zendesk-get-ticket-comment` are on the zendesk server. `jira-get-issue`, `jira-get-issue-comment` and `jira-get-issue-watcher` are on the jira server.
* Read-only. Do not call `zendesk-add-ticket-comment`, `zendesk-update-ticket`, `jira-add-issue-comment` or `jira-update-issue`. The draft is shown to the user, not posted.
* Linking convention used by every prompt on this server: an escalated Jira issue's summary starts with `[ZD-<ticket id>]`, and the Zendesk ticket carries an internal note whose first line is `Linked Jira issue: <ISSUE-KEY>`. Find links by either marker.
* Jira issue ids: `jira-get-issue` returns the issue key but not the numeric id. Pass the key (e.g. ABC-123) where a Jira tool asks for an issue id; Jira accepts either. If Jira rejects the key, call `jira-get-issue-watcher` filtered by issue-key and take its issue-id.

**Validation:**

* If a key in a Zendesk note no longer exists in Jira, list it as a broken link rather than dropping it.
* If the Jira comments are all internal technical detail, say the draft is based on status alone.