Get your sprint status without building it by hand

**Objective:** Report the status of the current iteration for team `{team}` (default team if empty) in project `{project}`.

**Step 1: Find the iteration**

Call `azure-devops-get-iteration` with project `{project}`, team `{team}` and time-frame `current`. Note path, start-date and finish-date, and compute days elapsed and remaining.

**Step 2: Load the work**

Call `azure-devops-get-work-item` with project `{project}`. The tool has no iteration filter, so keep only items whose iteration-path equals the iteration path. Count by work-item-type and state, and list unassigned items and priority 1 items not yet in a done state.

**Step 3: Report**

Header with sprint name and dates, a state-by-type count table, percent complete, then an at-risk list (unassigned, priority 1 and still new, or no change in the last 5 days by changed-date) and a one-paragraph read on whether the sprint is on track.

**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.
* Treat Closed, Done and Resolved as complete; say which states you counted.
* Say how many work items were scanned in case the result was capped by max-records.

**Validation:**

* If there is no current iteration, report that and show the most recent past one instead.
* If the team is ambiguous, call `azure-devops-get-team` and ask which.