Spot overloaded team members before the sprint slips

**Objective:** Compare capacity with assigned work for team `{team}` in project `{project}` for the current iteration.

**Step 1: Find the iteration and members**

Call `azure-devops-get-iteration` with project `{project}`, team `{team}` and time-frame `current`, then `azure-devops-get-team-member` with team-name `{team}` and project-name `{project}`.

**Step 2: Read capacity**

Call `azure-devops-get-capacity` with iteration-id, team `{team}` and project `{project}`. Compute available days as working days in the iteration minus total-days-off, and hours as total-capacity-per-day times that.

**Step 3: Read load**

Call `azure-devops-get-work-item` with project `{project}` and assigned-to for each member; keep items in the current iteration-path that are not done. Count items and priority 1 items per person.

**Step 4: Report**

A per-person table of available days, open items and priority 1 items, flagging anyone with no capacity but assigned work, or far more items than peers, and a closing note on unassigned items in the iteration.

**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.
* Item counts are a proxy; remaining-work hours are not available, so say so.

**Validation:**

* If no capacity is configured for the iteration, report that and stop after Step 2.