Catch ServiceNow escalations that stalled in Jira

**Objective:** Find ServiceNow incidents and problems escalated to Jira whose Jira issue has not been updated in `{stale-days}` days (default 14), or where one side is finished and the other is not, optionally limited to Jira project `{project-key}` and ServiceNow assignment group `{assignment-group}`. Read only.

**Step 1: Find the Jira issues that carry a ServiceNow number**

The link between the two systems is the ServiceNow number in the Jira summary, written as `[INC0010023]` or `[PRB0040012]`. Call `jira-get-issue` twice, once with `summary.contains` set to INC and once with PRB, filtered by `project-key` when `{project-key}` is given. Keep only issues whose summary actually contains a number of the form INC or PRB followed by digits, and extract that number.

**Step 2: Read each ServiceNow record**

For each extracted number, call `servicenow-get-incident` (INC) or `servicenow-get-problem` (PRB) filtered by `number`, and by `assignment-group` when `{assignment-group}` is given. If the record is not found, report the Jira issue as pointing at a ServiceNow record that does not exist (or is outside the group) and continue.

**Step 3: Classify**

For each pair, put it in at most one bucket:

* **Stale:** the ServiceNow record is open (not Resolved, Closed or Canceled) and the Jira issue's `updated-date` is more than `{stale-days}` days ago (default 14) and its status is not Done.
* **Jira done, ServiceNow open:** the Jira status is Done (or another resolved status) and the ServiceNow record is still open.
* **ServiceNow closed, Jira open:** the ServiceNow record is Resolved, Closed or Canceled and the Jira issue is still open.

For stale issues, call `jira-get-issue-comment` for the issue (pass the issue key as `issue-id`) to read the latest comment and its author.

**Step 4: Report**

One table per bucket: ServiceNow number, priority, state, assignment group; Jira key, status, assignee, days since update; and for stale issues the latest comment date and author. End with a count per bucket and the oldest stale pair.

**Rules & Guidelines:**

* `servicenow-get-incident` and `servicenow-get-problem` are on the servicenow server. `jira-get-issue` and `jira-get-issue-comment` are on the jira server.
* This prompt is read only. Do not call `servicenow-update-incident`, `servicenow-update-problem`, `jira-update-issue`, `jira-add-issue-comment` or `jira-assign-issue`.

**Validation:**

* If no Jira issue carries a ServiceNow number, say that no escalations were found and stop.
* If `jira-get-issue-comment` rejects the key as `issue-id`, read the numeric id with `jira-get-issue-watcher` filtered by `issue-key`; if that also finds nothing, report the comment as unavailable and continue.
* If one Jira issue mentions several ServiceNow numbers, check each one.