See how a work item got to where it is

**Objective:** Explain the history of work item `{work-item-id}`: who changed what and when, and why it is in its current state.

**Step 1: Load the item**

Call `azure-devops-get-work-item` with id `{work-item-id}`. Note type, title, state, assigned-to, area-path and iteration-path.

**Step 2: Load history**

Call `azure-devops-get-work-item-revision` with work-item-id `{work-item-id}` and `azure-devops-get-work-item-comment` with work-item-id `{work-item-id}`. Merge them in time order.

**Step 3: Report**

A short summary paragraph, then a dated timeline of state changes, reassignments and comments (changed-by or created-by, what changed), and flags for reopenings, long idle gaps and repeated reassignment.

**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.
* Quote comment text only where it explains a decision.
* Revision rows show state and owner, not field-level diffs; do not claim more.

**Validation:**

* If the id is not found, call `azure-devops-get-work-item-deleted` with id `{work-item-id}` and say if it was deleted and by whom.