See who in a ServiceNow group is carrying too much

**Objective:** Show how the open incident load of `{assignment-group}` is distributed across its members and recommend rebalancing.

**Step 1: List the members**

Call `servicenow-get-group-member` with group `{assignment-group}`. For each member call `servicenow-get-user` with name set to the member to check active. Inactive members holding work are a finding.

**Step 2: Pull the open work**

Call `servicenow-get-incident` with assignment-group `{assignment-group}` for states New, In Progress and On Hold. Group the results by assigned-to, with a bucket for unassigned.

**Step 3: Weigh it**

Per member count open incidents and weight them: priority 1 = 4, priority 2 = 3, priority 3 = 2, others = 1. For the priority 1 and 2 incidents call `servicenow-get-task-sla` with task set to the number and active true and count at-risk SLAs.

**Step 4: Report**

* A table per member: name, active, open incidents, weighted load, priority 1-2 count, at-risk SLAs, oldest opened date.
* Unassigned incidents: count and the three oldest numbers.
* Recommendations: which specific incidents to move from the most loaded member to the least loaded active member, and any incident held by an inactive user.

**Rules & Guidelines:**

* Read-only. Do not call `servicenow-update-incident`, `servicenow-add-group-member`, `servicenow-update-group-member` or any other add- or update- tool. Suggest moves; the reassign-incident prompt performs them.
* Assignees who are not group members count as a finding, not as capacity.

**Validation:**

* If the group has no members, stop and ask for the exact group name.