Escalate Zendesk tickets to Jira once, linked both ways

**Objective:** Escalate Zendesk ticket {ticket-id} to a new Jira issue of type {issue-type} (default Bug) in project {project-key}, link the two records both ways, and record the escalation on the ticket.

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

Call `zendesk-get-ticket` with ticket-id {ticket-id}. If nothing comes back, report that the ticket does not exist and stop. Then call `zendesk-get-ticket-comment` with ticket-id {ticket-id} to read the conversation, oldest first.

**Step 2: Check it is not already escalated**

Call `zendesk-get-ticket-comment` with ticket-id {ticket-id} and public false, and look for a note starting `Linked Jira issue:`. Also call `jira-get-issue` with summary.contains `[ZD-{ticket-id}]`. If either finds an existing issue, report its key and status and stop. Do not create a duplicate.

**Step 3: Resolve the Jira targets (Jira)**

* Call `jira-get-project` with project-key {project-key} and take project-id. If there is no match, stop and say so.
* Call `jira-get-issue-type` with project-key {project-key} and name {issue-type} (use Bug if {issue-type} is empty) and take issue-type-id. If there is no match, list the project's issue types and stop.
* Optionally, take the ticket's assignee, find their email with `zendesk-get-user`, then call `jira-get-user` with that email and use user-account-id as the reporter. If there is no match, leave the reporter unset.

**Step 4: Confirm, then create**

Show the user the summary you will use, `[ZD-{ticket-id}] <ticket subject>`, the project, the issue type, and a 3 to 6 line description drawn from the ticket (problem, customer organization, steps or evidence, priority). Wait for explicit confirmation. Then:

1. Call `jira-add-issue` once with project-id, issue-type-id, summary and (if found) reporter-account-id.
2. It returns nothing, so call `jira-get-issue` with project-key {project-key} and summary.contains `[ZD-{ticket-id}]` to get the new issue key.
3. Call `jira-add-issue-comment` on that issue with the description, the requester's organization and the Zendesk ticket id.
4. If {zendesk-subdomain} is not empty, call `jira-add-issue-remote-link` with url https://{zendesk-subdomain}.zendesk.com/agent/tickets/{ticket-id}, title Zendesk ticket {ticket-id}, application-name Zendesk and global-id zendesk-ticket-{ticket-id}. If it is empty, skip this step and say so.
5. Call `zendesk-add-ticket-comment` with ticket-id {ticket-id}, public false, and a body whose first line is `Linked Jira issue: <ISSUE-KEY>`.

**Step 5: Report**

The Jira issue key, project, type, which of steps 3 to 5 succeeded, and anything skipped.

**Rules & Guidelines:**

* `zendesk-get-ticket`, `zendesk-get-ticket-comment`, `zendesk-get-user` and `zendesk-add-ticket-comment` are on the zendesk server. `jira-get-project`, `jira-get-issue-type`, `jira-get-user`, `jira-get-issue`, `jira-add-issue`, `jira-add-issue-comment` and `jira-add-issue-remote-link` are on the jira server.
* Never post a public Zendesk comment from this prompt. The note in step 5.5 must have public false.
* Do not call `zendesk-update-ticket` or `jira-update-issue`. Do not change the ticket's status, tags or assignee.
* 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 `jira-add-issue` fails, stop before touching Zendesk and report the error.
* If the new issue cannot be found in step 4.2, do not retry the create. Report that the issue may have been created and ask the user to check the project.