Follow a reported bug all the way to the fix

**Objective:** Trace BugHerd task number `{task-number}` in project `{project-id}` to the code changes and builds that address it.

**Step 1: Find the task (BugHerd server)**

Call `bugherd-get-tasks` with project-id `{project-id}` and task-number `{task-number}`. If more than one record or none comes back, say so and stop. Note title, status, severity and external-id. If the task is not in the active list, try `bugherd-get-archived-tasks` with the same filters.

**Step 2: Find the work item (Azure DevOps server)**

If external-id is present, call `azure-devops-get-work-item` with id set to it. If not, call `azure-devops-get-work-item` with title.contains set to the key words of the task title and list the candidates, then continue only with a clear match.

**Step 3: Find pull requests and builds (Azure DevOps server)**

Call `azure-devops-get-pull-request` with title.contains set to the work item id. For each pull request found, note status, source-branch, target-branch and repository-id. Then call `azure-devops-get-build` with repository-id from the pull request and report the most recent builds with result-related fields available.

**Step 4: Report**

A timeline: BugHerd task, work item, pull requests, builds. End with one line saying whether a fix appears to have shipped.

**Rules & Guidelines:**

* `bugherd-get-tasks` and `bugherd-get-archived-tasks` are on the BugHerd server; `azure-devops-get-work-item`, `azure-devops-get-pull-request` and `azure-devops-get-build` are on the Azure DevOps server.
* Read only. Never call `bugherd-update-task`, `bugherd-move-task` or `bugherd-add-comment`.

**Validation:**

* If no work item or pull request is found, report the gap rather than guessing a link.
* Pull request titles that do not mention the work item id are not evidence; say the match is by title only.