Tell support the moment a Jira fix is finished

**Objective:** Find escalated issues in Jira project {project-key} that finished in the last {lookback-days} days (default 7) and whose Zendesk ticket is still open, and record the outcome on each ticket as an internal note.

**Step 1: Find finished escalations (Jira)**

Call `jira-get-issue` with project-key {project-key}, summary.contains `[ZD-`, and updated.from set to today minus {lookback-days} days (7 if empty). Keep issues whose status is Done, Closed or Resolved, and parse the ticket id from the `[ZD-<id>]` prefix.

**Step 2: Find tickets still waiting (Zendesk)**

For each ticket id, call `zendesk-get-ticket`. Keep the tickets whose status is not solved or closed. If none remain, report that everything is in sync and stop.

**Step 3: Gather the outcome (Jira)**

For each kept issue, call `jira-get-issue-comment` and take the most recent comment as the resolution detail.

**Step 4: Confirm, then write (Zendesk)**

Show the user a table of ticket id, Zendesk status, Jira key, Jira status and a one-line resolution. Wait for explicit confirmation, which may exclude rows. Then, for each confirmed row, call `zendesk-add-ticket-comment` once with ticket-id, public false and a body stating the Jira key, its status and the resolution detail.

Only if the user explicitly asks in their confirmation, call `zendesk-update-ticket` with id and status pending for those rows. Never set solved or closed.

**Step 5: Report**

The tickets noted, any changed to pending, and any that failed.

**Rules & Guidelines:**

* `jira-get-issue`, `jira-get-issue-comment` and `jira-get-issue-watcher` are on the jira server. `zendesk-get-ticket`, `zendesk-add-ticket-comment` and `zendesk-update-ticket` are on the zendesk server.
* Every Zendesk comment from this prompt is internal (public false). The customer is contacted by an agent, not by this prompt.
* Do not call any Jira write tool: not `jira-update-issue`, `jira-add-issue-comment` nor `jira-add-issue`.
* 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 ticket id cannot be found in Zendesk, list it and continue.
* If an issue has no comments, write the note from the status alone and say so.