Send BugHerd bugs to GitHub with full context

**Objective:** Open a GitHub issue in the repository `{repository}` for task `{task-number}` in the BugHerd project `{project-name}`, assigned to `{assignee-login}` when given, 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 `github-get-issue` with `company` set to `{repository}` and `title.contains` set to "[BugHerd" plus the project name and " #" plus the task number. If an issue exists, report its number, status and issue-url and stop.

**Step 3: Prepare the issue**

* title: "[BugHerd <project name> #<task number>] " plus the task title.
* body, in markdown: the task description; then a list with Page, Severity, Requester (email), Reported (created date) and "BugHerd task" with the admin-link.
* label: bug.

**Step 4: Confirm, then write**

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

1. Call `github-add-issue` once with `company`, `title`, `body`, `label` and `assignee` when given.
2. Call `github-get-issue` with `company` and `title.contains` set to the "[BugHerd ...]" prefix to read back the issue-number and issue-url.
3. Call `bugherd-add-comment` once with `project-id`, `task-id` and "Opened on GitHub as {repository}#<issue number>: <issue-url>".

**Step 5: Report**

The issue number and issue-url, and whether the BugHerd comment was added.

**Rules & Guidelines:**

* Tools named bugherd-... are on the bugherd MCP server; tools named github-... are on the github MCP server. Every GitHub tool takes the repository as its `company` parameter. If either set of tools is missing, say which server is not connected and stop.
* The only write tools this prompt may call are `github-add-issue` and `bugherd-add-comment`, each once, after the user confirms.
* If the repository has no "bug" label and `github-add-issue` fails because of it, retry once without `label` and say so.

**Validation:**

* If `github-add-issue` fails for any other reason, show the error and stop.