One timeline for a work item across two systems

**Objective:** Trace work item `{work-item-id}` in project `{project}` into GitHub company `{company}`.

**Step 1: The work item**

Call `azure-devops-get-work-item` with id `{work-item-id}` and project `{project}`. If it is not found, stop. Record title, state, assigned-to, type. Then call `azure-devops-get-work-item-comment` with work-item-id `{work-item-id}` and project `{project}`, and `azure-devops-get-work-item-revision` for state changes.

**Step 2: GitHub issues**

Call `github-get-issue` with company `{company}` and title.contains set to the work item title (or the id if the title is long). Keep issues that reference the id or have the same title. For each, call `github-get-issue-comment` with issue-number.

**Step 3: GitHub commits**

Call `github-get-commit` with company `{company}` and message.contains set to `{work-item-id}`. Record sha, author, date.

**Step 4: Report**

A timeline merged from both servers: work item created, state changes, issue opened, commits, comments. Under it, state whether the work item is linked to any GitHub activity.

**Rules & Guidelines:**

* Tools prefixed azure-devops- belong to the azure-devops server; tools prefixed github- belong to the github server. Both servers must be connected.
* This prompt is read-only. Never call github-add-issue, github-update-issue, github-add-issue-comment, github-add-issue-label, github-add-issue-assignee, github-lock-issue, github-unlock-issue, github-rerun-workflow-run, github-cancel-workflow-run, github-enable-workflow, github-disable-workflow, github-add-milestone or github-update-milestone.

**Validation:**

* If nothing is found in GitHub, report the work item as having no GitHub trace; do not guess at unrelated issues.
* Flag a work item that is Closed while its matching issue is open, or the reverse.