Catch Zendesk tickets out of step with their Jira issues

**Objective:** For Jira project {project-key}, compare every escalated issue updated in the last {lookback-days} days (default 30) with its Zendesk ticket, and report where the two systems disagree.

**Step 1: List escalated issues (Jira)**

Call `jira-get-issue` with project-key {project-key}, summary.contains `[ZD-` and updated.from set to today minus {lookback-days} days (30 if empty). Parse the ticket id from each summary's `[ZD-<id>]` prefix. If none come back, report that no escalations were found and stop.

**Step 2: Read each ticket (Zendesk)**

For each ticket id, call `zendesk-get-ticket` with ticket-id. Keep status, priority, assignee and updated date.

**Step 3: Classify each pair**

Treat Jira statuses Done, Closed or Resolved as finished, and Zendesk statuses solved or closed as finished.

* **Customer waiting on a finished fix:** Jira finished, Zendesk not finished.
* **Closed too early:** Zendesk finished, Jira not finished.
* **Orphan:** the ticket id is not found in Zendesk.
* **Priority mismatch:** Zendesk priority urgent or high while the Jira issue has no assignee.
* **Consistent:** everything else. Count these but do not list them.

**Step 4: Report**

One table per category with Jira key, Jira status, Jira assignee, ticket id, Zendesk status, Zendesk assignee and days since the last update on either side. Lead with the customer-waiting group.

**Rules & Guidelines:**

* `jira-get-issue` is on the jira server. `zendesk-get-ticket` is on the zendesk server.
* Read-only. Do not call `zendesk-update-ticket`, `zendesk-add-ticket-comment`, `jira-update-issue` or `jira-add-issue-comment`. To act on a row, the user can run sync-resolved-escalations.
* Tickets linked only by a Zendesk note (see link-ticket-to-issue) are not found from the Jira side. Say so in the report footer.
* Linking convention used by every prompt on this server: an escalated Jira issue's summary starts with `[ZD-<ticket id>]`, and the Zendesk ticket carries an internal note whose first line is `Linked Jira issue: <ISSUE-KEY>`. Find links by either marker.
* Jira issue ids: `jira-get-issue` returns the issue key but not the numeric id. Pass the key (e.g. ABC-123) where a Jira tool asks for an issue id; Jira accepts either. If Jira rejects the key, call `jira-get-issue-watcher` filtered by issue-key and take its issue-id.

**Validation:**

* If a summary contains `[ZD-` but no number can be parsed, list it under Orphan with the raw summary.
* If a Jira status name does not fit the finished list, treat it as not finished and name it in the footer.