See Jira issue delivery status from Azure DevOps

**Objective:** For Jira project `{project-key}`, take the issues in status `{status}` (default: In Review) and show what Azure DevOps says about their delivery, looking at up to `{max-records}` issues (default 20).

**Step 1: Read the issues on Jira**

Call `jira-get-issue` (Jira server) with `project-key` set to `{project-key}`, `status` set to `{status}` and `max-records` set to `{max-records}`. Keep `issue-key`, `summary`, `assignee` and `updated-date`. If nothing comes back, say so and stop.

**Step 2: Look each issue up on Azure DevOps**

For each issue, call `azure-devops-get-pull-request` (Azure DevOps server) with `title.contains` set to the `issue-key`. Note each pull request `status`, `merge-status`, `is-draft`, `repository-name` and `target-branch`. For each repository found, call `azure-devops-get-build` (Azure DevOps server) with `repository-name` set to it and `max-records` 5 to note the latest build result.

**Step 3: Report**

Produce a table: Jira key, summary, assignee, pull request id and status, latest build result, and a Delivery column holding Merged and built, Merged build failing, Open pull request, Draft only or No pull request. List first the issues in Delivery states that need attention.

**Rules & Guidelines:**

* `jira-*` tools are on the Jira server and `azure-devops-*` tools are on the Azure DevOps server.
* This prompt is read only. Never call `jira-update-issue`, `jira-add-issue-comment`, `jira-assign-issue` or any other write tool.
* Match pull requests on the full issue key in the title only.

**Validation:**

* If an issue has no pull request, record No pull request and continue.
* If a repository has no builds, record No build rather than treating it as a failure.