Escalate website bugs to ServiceNow once, with the link kept

**Objective:** Raise a ServiceNow incident for task `{task-number}` in the BugHerd project `{project-name}`, assigned to `{assignment-group}` when given, and record the link on both sides.

**Step 1: Read the BugHerd 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` with `project-id` and `task-number`. If it is not found, say so and stop.

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

* If the task's external-id holds an incident number, call `servicenow-get-incident` with `number` set to it, report that incident (number, state, assigned-to) and stop.
* Call `servicenow-get-incident` with `short-description.contains` set to "[BugHerd" plus the project name and " #" plus the task number. If one exists, report it and stop.

**Step 3: Prepare the incident**

* Caller: call `servicenow-get-user` with `email` set to the task's requester-email. Use the matching user's sys-id. If no user matches, leave caller empty and say so.
* Map BugHerd severity to ServiceNow impact and urgency, choosing from the listed values: critical = high impact, high urgency; important = medium impact, high urgency; normal = medium impact, medium urgency; minor or not set = low impact, low urgency.
* short-description: "[BugHerd <project name> #<task number>] " followed by the task title (or the first 80 characters of the description when there is no title).
* description: the task description, then the page, then "BugHerd task: " and the admin-link.

**Step 4: Confirm, then write**

Show the incident you will create and wait for an explicit yes. Then:

1. Call `servicenow-add-incident` once with `short-description`, `description`, `impact`, `urgency`, `caller` when found, and `assignment-group` when given.
2. Call `servicenow-get-incident` with `short-description.contains` set to the "[BugHerd ...]" prefix to read back the new incident's number.
3. Call `bugherd-add-comment` once with `project-id`, `task-id` and the comment "Escalated to ServiceNow incident <number>."

**Step 5: Report**

The incident number, its state, and confirmation that the BugHerd comment was added.

**Rules & Guidelines:**

* Tools named bugherd-... are on the bugherd MCP server; tools named servicenow-... are on the servicenow 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 `servicenow-add-incident` (once) and `bugherd-add-comment` (once), after the user confirms.
* Do not change the BugHerd task's status, severity or assignee.

**Validation:**

* If `servicenow-add-incident` fails, show the error and do not add the BugHerd comment.
* If the incident cannot be read back, still add the comment, saying the incident number could not be confirmed.