Hand Zendesk website problems to the web team in BugHerd

**Objective:** Create a BugHerd task in the project `{project-name}` for Zendesk ticket `{ticket-id}`, with severity `{severity}` (judged from the ticket when empty), and note it on the ticket.

How the two systems are linked: a BugHerd task created from a Zendesk ticket carries "zendesk:<ticket id>" in its external-id, and the ticket gets a private note naming the task. When a ticket is raised from a BugHerd task, the task gets a comment naming the ticket.

**Step 1: Read the ticket**

Call `zendesk-get-ticket` with `ticket-id` set to `{ticket-id}`. If it is not found, stop. Call `zendesk-get-ticket-comment` with `ticket-id` to read the conversation, and `zendesk-get-ticket-comment-attachment` with `ticket-id` for any screenshots.

**Step 2: Check for an existing task**

Call `bugherd-get-projects` with `name.contains` set to `{project-name}`. If nothing matches, say so and stop. If several match, list their names and project-id values and ask which one; do not guess. Then call `bugherd-get-tasks` and `bugherd-get-feedback` with `project-id` and `external-id` set to "zendesk:{ticket-id}". If a task exists, report it and stop.

**Step 3: Prepare the task**

* description: the ticket subject; then a plain summary of the problem from the customer's comments (what page, what they did, what went wrong); then "Zendesk ticket {ticket-id}, organization <organization-name>, priority <priority>". Leave out personal data beyond the requester's email.
* severity: `{severity}` when given; otherwise urgent priority = critical, high = important, normal = normal, low = minor.
* requester-email: the ticket's requester-email.

**Step 4: Confirm, then write**

Show the task and wait for an explicit yes. Then:

1. Call `bugherd-add-task` once with `project-id`, `description`, `severity`, `requester-email` and `external-id` "zendesk:{ticket-id}".
2. Call `bugherd-get-tasks` with `project-id` and `external-id` to read back the task number and admin-link.
3. For each screenshot attachment with an image content-type, call `bugherd-add-attachment-from-url` with `project-id`, `task-id`, `url` set to its content-url and `file-name`. Skip this if the content-url needs a Zendesk login to open; say so.
4. Call `zendesk-add-ticket-comment` once with `ticket-id`, `public` false and `body` "Logged for the web team in BugHerd as task #<task number>: <admin-link>".

**Step 5: Report**

The task number and admin-link, attachments added, and whether the private note was added.

**Rules & Guidelines:**

* Tools named bugherd-... are on the bugherd MCP server; tools named zendesk-... are on the zendesk MCP server. If either set of tools is missing, say which server is not connected and stop.
* The only write tools this prompt may call are `bugherd-add-task` (once), `bugherd-add-attachment-from-url` and `zendesk-add-ticket-comment` (once, private), after the user confirms.
* Never post a public reply or change the ticket's status here.

**Validation:**

* If `bugherd-add-task` fails, show the error and do not touch Zendesk.