Bring BugHerd tasks and Jira issues back in step

**Objective:** Bring linked items in the BugHerd project `{project-name}` and the Jira project `{jira-project-key}` back in step.

How the two systems are linked: a BugHerd task created from a Jira issue carries the issue key (e.g. WEB-123) in its external-id. A Jira issue created from BugHerd starts its summary with "[BugHerd <project name> #<task number>]" and has a remote link to the task.

**Step 1: Find the drifted pairs**

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 read the links as the reconcile job does: `bugherd-get-tasks` and `bugherd-get-archived-tasks` with `project-id` (keep tasks whose external-id starts with `{jira-project-key}-`), and `jira-get-issue` with `project-key` and `summary.contains` "[BugHerd". Pair them and keep the pairs where exactly one side is finished.

**Step 2: Propose**

* Done in Jira, open in BugHerd: set the task's status to done and comment "Jira issue <key> is <status>."
* Done in BugHerd, open in Jira: add a Jira comment "BugHerd task #<task number> is done; please verify and close." Do not change the Jira status: workflow transitions are left to the Jira team.

Show every proposal in one table and ask which rows to apply.

**Step 3: Apply approved rows**

* BugHerd: call `bugherd-update-task` once with `project-id`, `task-id` and `status` done, then `bugherd-add-comment` once.
* Jira: call `jira-add-issue-comment` once with `issue-id` set to the issue key and `body`.

**Step 4: Report**

What was changed on each side and anything that failed, with the error.

**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-update-task`, `bugherd-add-comment` and `jira-add-issue-comment`, and only for approved rows.
* Never reopen anything and never call `jira-update-issue`.

**Validation:**

* If nothing has drifted, say so and stop.
* If one update fails, report it and carry on with the other rows.