Bring Jira issues onto the BugHerd board without retyping

**Objective:** Create a BugHerd task in the project `{project-name}` for the Jira issue `{issue-key}`, and link the task back on the issue.

**Step 1: Read the issue**

Call `jira-get-issue` with `issue-key` set to `{issue-key}`. If it is not found, say so and stop. If its status is done or closed, say so and ask whether to continue.

**Step 2: Find the project and 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` with `project-id` and `external-id` set to `{issue-key}`. If a task exists, report its task number and admin-link and stop.

**Step 3: Prepare the task**

* description: the issue summary, a blank line, the issue description, then "Jira issue " plus the key.
* severity: normal unless the summary or description says the site is down or unusable (critical) or it blocks a key page (important).
* assignee: if the issue has an assignee, call `jira-get-user` with `name.contains` to get their email and pass it as `assignee-email`.

**Step 4: Confirm, then write**

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

1. Call `bugherd-add-task` once with `project-id`, `description`, `severity`, `external-id` set to `{issue-key}`, and `assignee-email` when found.
2. Call `bugherd-get-tasks` with `project-id` and `external-id` set to `{issue-key}` to read back the task's admin-link.
3. Call `jira-add-issue-remote-link` once with `issue-id` set to `{issue-key}`, `url` set to the admin-link, `title` "BugHerd task #<task number>" and `application-name` BugHerd.

**Step 5: Report**

The BugHerd task number and admin-link, and whether the remote link was added.

**Rules & Guidelines:**

* Tools named bugherd-... are on the bugherd MCP server; tools named jira-... are on the jira MCP server. If either set of tools is missing, say which server is not connected and stop.
* Jira write tools ask for a numeric issue id, which `jira-get-issue` does not return. Pass the issue key (e.g. WEB-123) as the id instead: Jira accepts a key wherever an issue id is asked for.
* The only write tools this prompt may call are `bugherd-add-task` and `jira-add-issue-remote-link`, each once, after the user confirms.
* Never change the Jira issue's fields or status.

**Validation:**

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