Know which ServiceNow changes still have open Jira work

**Objective:** For ServiceNow change requests planned to start in the next `{days-ahead}` days (default 14), optionally for assignment group `{assignment-group}`, check whether the Jira work they deploy is finished, optionally limited to Jira project `{project-key}`. Read only.

**Step 1: Read the upcoming changes**

Call `servicenow-get-change-request` with `planned-start-date.from` set to today and `planned-start-date.to` set to `{days-ahead}` days from today (default 14), filtered by `assignment-group` when `{assignment-group}` is given. Ignore changes that are Closed or Canceled. If none come back, say so and stop.

**Step 2: Find the Jira issues in each change**

The link between the two systems is the change number (CHG followed by digits) written into the Jira summary or added as a Jira label. For each change, call `jira-get-issue` with `summary.contains` set to the change number, filtered by `project-key` when given. If `{project-key}` is given, also call `jira-get-issue` for that project and keep any issue whose `labels` contain the change number. Jira release (fix version) data is not available on this server, so match only on the change number.

For each change, also call `servicenow-get-change-task` filtered by `change-request` to see its open tasks.

**Step 3: Classify each change**

* **Ready:** every linked Jira issue is Done.
* **At risk:** at least one linked Jira issue is not Done. List those issues.
* **No Jira work found:** no issue carries the change number. Normal changes with code should have one.

**Step 4: Report**

One row per change: number, short description, type, risk, approval, planned start, assignment group, open change tasks, readiness, and the Jira keys with status and assignee. Sort by planned start. End with counts per readiness bucket and the soonest at-risk change.

**Rules & Guidelines:**

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

**Validation:**

* If a change's approval is not Approved, say so in the row even when the Jira work is ready.
* If a Jira issue carries several change numbers, list it under each change.
* If Jira returns nothing for every change, say that no Jira issue references these changes and suggest the `plan-change-from-jira-issues` prompt.