Send website bugs to Jira once, with the full detail

**Objective:** Create a Jira issue in the project `{jira-project-key}` (type `{issue-type}`, default Bug) for task `{task-number}` in the BugHerd project `{project-name}`, and link the two.

**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 has not been sent already**

Call `jira-get-issue` with `project-key` set to `{jira-project-key}` and `summary.contains` set to "[BugHerd" plus the project name and " #" plus the task number. If an issue exists, report its key and status and stop.

**Step 3: Resolve the Jira side**

* Call `jira-get-project` with `project-key` to get its project-id. If it does not exist, stop.
* Call `jira-get-issue-type` with `project-key` and `name` set to the issue type. Use its issue-type-id; if there is no match, list the project's issue types and ask.
* Assignee: if the task has an assignee, call `bugherd-get-users` to find that user's email, then `jira-get-user` with `email`. Use the user-account-id when exactly one matches; otherwise leave the issue unassigned and say so.

**Step 4: Confirm, then write**

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

1. Call `jira-add-issue` once with `project-id`, `issue-type-id`, `summary` set to "[BugHerd <project name> #<task number>] " plus the task title, `due-date` from the task when it has one, and `assignee-account-id` when found.
2. Call `jira-get-issue` with `summary.contains` set to the "[BugHerd ...]" prefix to read back the new issue key.
3. Call `jira-update-issue` once with `id` set to the issue key and `description` set to the task description, the page, the requester email and the severity.
4. Call `jira-add-issue-remote-link` once with `issue-id` set to the issue key, `url` set to the task's admin-link, `title` "BugHerd task #<task number>", `application-name` BugHerd and `global-id` "bugherd-<project-id>-<task number>".
5. Call `bugherd-add-comment` once with `project-id`, `task-id` and "Sent to Jira as <issue key>."

**Step 5: Report**

The Jira issue key, its status and assignee, and which of steps 3 to 5 succeeded.

**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 `jira-add-issue`, `jira-update-issue`, `jira-add-issue-remote-link` and `bugherd-add-comment`, each once, after the user confirms.
* Do not change the BugHerd task's status, severity or assignee.

**Validation:**

* If `jira-add-issue` fails, show the error and stop; write nothing else.
* If the new issue cannot be read back, stop after reporting that it was created and that the link steps were skipped.