Find BugHerd tasks and ServiceNow incidents out of step

**Objective:** For the BugHerd project `{project-name}`, find every BugHerd task linked to a ServiceNow incident (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 an incident carries the incident number (INC...) in its external-id. An incident escalated from BugHerd starts its short-description with "[BugHerd <project name> #<task number>]".

**Step 1: Collect the 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 INC.

**Step 2: Collect the links from ServiceNow**

Call `servicenow-get-incident` with `short-description.contains` set to "[BugHerd" plus the project name and `opened.from` set to the start of the period. Read the task number from each prefix.

**Step 3: Pair them up**

For each link, read the other side: `servicenow-get-incident` with `number`, or `bugherd-get-tasks` (then `bugherd-get-archived-tasks`) with `project-id` and `task-number`.

Classify each pair:

* **In step:** both open, or both finished (BugHerd done, closed or archived; ServiceNow resolved, closed or canceled).
* **Fixed in BugHerd, open in ServiceNow:** the incident can probably be resolved.
* **Resolved in ServiceNow, open in BugHerd:** check whether the fix is real before closing the task.
* **Broken link:** the number points at nothing on the other side.

**Step 4: Report**

One table per class except "in step" (give that as a count): BugHerd task number, title, BugHerd status, incident number, incident state, assigned-to on each side.

**Rules & Guidelines:**

* Tools named bugherd-... are on the bugherd MCP server; tools named servicenow-... are on the servicenow 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 ServiceNow write tool (any tool named servicenow-add-... or servicenow-update-..., including `servicenow-add-incident`, `servicenow-update-incident`, `servicenow-add-problem`, `servicenow-update-problem`, `servicenow-update-change-request`). To act on the result, use `sync-bug-incident-status`.

**Validation:**

* If no links are found on either side, say so and stop.
* Incident numbers are compared exactly; ignore case and surrounding spaces.