Reassign and escalate BugHerd tasks with a note attached

**Objective:** Update task `{task-number}` in the BugHerd project `{project-name}`: assign it to `{assignee-name}` and set severity `{severity}`, keeping whatever is left empty.

**Step 1: Find the project**

Call `bugherd-get-projects` with `name.contains` set to `{project-name}`. If nothing matches, say so and stop. If more than one project matches, list their names and project-id values and ask which one is meant; do not guess. Use the matching project's project-id in every later call.

**Step 2: Read the task**

Call `bugherd-get-tasks` with `project-id` and `task-number`. If it is not found, say so and stop. Note its task-id, current assignee, severity and status.

**Step 3: Resolve the new assignee**

If `{assignee-name}` is given, call `bugherd-get-users` with `display-name.contains`. If several people match, list them and ask which one. Take their user-id.

**Step 4: Confirm, then write**

Show current and new values side by side and wait for an explicit yes. Then:

* Call `bugherd-update-task` once with `project-id`, `task-id`, and only the fields that change (`assignee-id`, `severity`).
* Call `bugherd-add-comment` once with `project-id`, `task-id` and a one-line note saying what changed, for example "Reassigned to Jane and raised to critical."

**Step 5: Report**

What changed, and the note that was added.

**Rules & Guidelines:**

* The only write tools this prompt may call are `bugherd-update-task` and `bugherd-add-comment`, each once, after the user confirms.
* If nothing would change, say so and do not write.

**Validation:**

* If `bugherd-update-task` fails, do not add the comment; show the error.