Bring GitHub issues into BugHerd, linked both ways

**Objective:** Create a BugHerd task in the project `{project-name}` for GitHub issue `{issue-number}` in the repository `{repository}`, and link it back on the issue.

**Step 1: Read the issue**

Call `github-get-issue` with `company` set to `{repository}` and `issue-number`. If it is not found, say so and stop. If its status is 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 "{repository}#{issue-number}". If a task exists, report its task number and admin-link and stop.

**Step 3: Prepare the task**

* description: the issue title, a blank line, the issue body (cut to 2000 characters), then the issue-url.
* severity: critical if the issue's labels include critical, blocker or p0; important for high or p1; otherwise normal.

**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` and `external-id` set to "{repository}#{issue-number}".
2. Call `bugherd-get-tasks` with `project-id` and `external-id` to read back the task number and admin-link.
3. Call `github-add-issue-comment` once with `company`, `issue-number` and "Tracked in BugHerd as task #<task number>: <admin-link>".

**Step 5: Report**

The BugHerd task number and admin-link, and whether the GitHub 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 `bugherd-add-task` and `github-add-issue-comment`, each once, after the user confirms.
* Do not change the GitHub issue's state, labels or assignee.

**Validation:**

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