Know if a pull request can merge in one answer

**Objective:** Decide whether pull request `{pull-request-id}` (repository `{repository-name}` if given) is ready to merge, and list what is missing if not.

**Step 1: Load the pull request**

Call `azure-devops-get-pull-request` with id `{pull-request-id}`. If more than one repository matches, list them and stop. Note status, is-draft, merge-status, source-branch and target-branch.

**Step 2: Check reviews**

Call `azure-devops-get-pull-request-reviewer` with the pull-request-id and repository-id. Required reviewers must have an approving vote. Treat any rejected or waiting vote as blocking.

**Step 3: Check discussion**

Call `azure-devops-get-pull-request-thread` for the pull request and count threads whose status is active or pending, grouped by file-path.

**Step 4: Report**

Verdict (ready, ready with caveats, or not ready), then a checklist: status, draft, merge-status, required reviews, unresolved threads, and the exact items blocking the merge.

**Rules & Guidelines:**

* This prompt is read-only. Call only the `azure-devops-get-*` read tools named above; never create, update, comment on, approve, queue, abort or delete anything in Azure DevOps.
* The tools only return data the connected account can see; never infer data from projects outside that access.
* Do not tell the user to merge or complete it; only report readiness.
* Base every statement on tool output, not on the title or description.

**Validation:**

* If the pull request is already completed or abandoned, say so and stop after Step 1.
* If the id is not found, report that and stop.