See which incidents relate to a work item

**Objective:** Trace Azure DevOps work item `{work-item-id}` to the ServiceNow incidents and problems that reference it, opened in the last `{lookback-days}` days (default 90).

**Step 1: Establish the work item (azure-devops server)**

Call `azure-devops-get-work-item` with `id` = {work-item-id}. If nothing comes back, report that the work item does not exist and stop. Keep its `title`, `state`, `assigned-to`, `priority` and `project`. Then call `azure-devops-get-work-item-comment` with `work-item-id` = {work-item-id} and note any text that mentions a ServiceNow number (INC, PRB, CHG).

**Step 2: Search ServiceNow (servicenow server)**

ServiceNow has no work item id field, so match on text. Call `servicenow-get-incident` with `short-description.contains` = {work-item-id}, and `opened.from` set to the lookback start. Repeat with the work item title as `short-description.contains`. Do the same with `servicenow-get-problem`. Also fetch any INC or PRB number found in Step 1 by passing it as `number`. Merge duplicates by `number`.

**Step 3: Report**

Give the work item summary, then a table of matching records: `number`, record type, `short-description`, `state`, `priority`, `assigned-to`, `opened`, and how it matched (id in text, title, or number in a comment). Mark title-only matches as probable, not confirmed.

**Rules & Guidelines:**

* `azure-devops-get-work-item` and `azure-devops-get-work-item-comment` are on the azure-devops server. `servicenow-get-incident` and `servicenow-get-problem` are on the servicenow server.
* This prompt is read-only. Do NOT call any `servicenow-add-*` or `servicenow-update-*` tool.

**Validation:**

* If ServiceNow returns nothing, report the work item as having no linked incident or problem and do not guess.
* If a number is more than 6 digits long, check it is the work item id and not an unrelated number before treating it as a match.