See who on your team has been missed by Chorus reviews

**Objective:** Audit review coverage for the team `{team-name}` over the last `{lookback-days}` days (default 30): who has been scored, who has been missed, and whether the reviewing is spread or concentrated.

**Step 1: Establish the team roster**

Call `chorus-get-teams` with `name.contains` set to `{team-name}`. If more than one team matches, list them and stop. Then call `chorus-get-team-members` with `team-name` set to the exact team name, and keep every `user-id`.

**Step 2: Turn the roster into people**

For each `user-id`, call `chorus-get-users` with `user-id` set to that value. Keep `name`, `email`, `role`, `license-type` and `active`. Exclude anyone whose `active` is false from the coverage denominator, but list them separately as roster cleanup.

**Step 3: Measure activity**

For each active member, call `chorus-get-engagements` with `user-email` set to their email and `date.from` set to the start of the window. Count the conversations. Someone with no conversations cannot be reviewed, and that is a different problem from not being reviewed.

**Step 4: Measure review coverage**

For each active member, call `chorus-get-scorecards` with `recipient-name` set to their exact name and `submitted.from` set to the start of the window. Count the scorecards and note every `reviewer-name`. Then call `chorus-get-moments` the same way to count coaching moments.

**Step 5: Report**

Produce:

* **Coverage table** - one row per active member: name, role, conversations, scorecards, coaching moments, most recent review date.
* **Not reviewed** - members with conversations in the window but no scorecard, listed first. This is the headline.
* **No activity** - members with no conversations at all, since the cause is elsewhere.
* **Reviewer load** - a count per `reviewer-name`, to show whether one person is carrying the reviewing.
* **Recommendation** - who to review next and why.

**Rules & Guidelines:**

* This is read only. Do not call any tool that creates, updates or exports.
* Count, do not estimate. If a member's list is empty, the count is zero and you say so.
* A member being on the roster is not the same as being active. Keep those two columns distinct.

**Validation:**

* If `{team-name}` matches no team, list the teams that exist and stop.
* If the team has no members, report that the team record is empty rather than reporting full coverage.