Spot BugHerd tasks and Jira issues that have drifted apart

**Objective:** Find every link between the BugHerd project `{project-name}` and the Jira project `{jira-project-key}` created in the last `{lookback-days}` days (default 90), and report where the two disagree.

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: Links from BugHerd**

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` and `bugherd-get-archived-tasks` with `project-id`, `created.from` set to the start of the period and `max-records` 500. Keep tasks whose external-id starts with `{jira-project-key}` followed by a dash.

**Step 2: Links from Jira**

Call `jira-get-issue` with `project-key` set to `{jira-project-key}`, `summary.contains` set to "[BugHerd" and `created.from` set to the start of the period. Read the BugHerd task number from each summary prefix.

**Step 3: Pair them up**

For each link, read the other side: `jira-get-issue` with `issue-key`, or `bugherd-get-tasks` (then `bugherd-get-archived-tasks`) with `project-id` and `task-number`. Treat a task as finished when it is BugHerd done or closed, or the task is archived, and an issue as finished when it has a Jira status such as Done, Closed or Resolved.

* **In step:** both open or both finished.
* **Done in Jira, open in BugHerd:** the fix may be ready to verify on the site.
* **Done in BugHerd, open in Jira:** the Jira issue is probably stale.
* **Broken link:** the key or task number points at nothing.

**Step 4: Report**

One table per class except "in step" (give that as a count): task number, task title, BugHerd status, issue key, Jira status, assignee on each side.

**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.
* This prompt is read-only. Do not call any BugHerd write tool (`bugherd-add-task`, `bugherd-add-feedback`, `bugherd-update-task`, `bugherd-move-task`, `bugherd-add-comment`, `bugherd-add-attachment-from-url`, `bugherd-add-project`, `bugherd-update-project`, `bugherd-add-project-member`, `bugherd-add-guest-to-project`) or any Jira write tool (`jira-add-issue`, `jira-update-issue`, `jira-assign-issue`, `jira-add-issue-comment`, `jira-update-issue-comment`, `jira-add-issue-remote-link`, `jira-add-issue-watcher`, `jira-add-issue-worklog`, `jira-add-issue-vote`, `jira-add-project`, `jira-update-project`). To act on the result, use `sync-bugherd-jira-status`.

**Validation:**

* If there are no links on either side, say so and stop.