Reach troubled Teamwork.com clients before they escalate

**Objective:** List the clients whose Teamwork projects are in trouble and who have had no Chorus call or email in the last `{quiet-days}` days (default 21), so someone can reach out before it escalates. Treat a health score at or below `{health-threshold}` (default 50) as unhealthy.

**Step 1: Find the troubled projects in Teamwork**

Call `teamwork-get-project-health` with `health-score.max` set to the threshold. Then call `teamwork-get-milestones` with `completed` false and `deadline.to` set to yesterday to find late milestones. Collect the `project-id` values from both.

**Step 2: Resolve each project to its client**

Call `teamwork-get-projects` with each `project-id` and keep `project-name`, `company-name`, `company-id` and `status`. Ignore projects whose status is completed or archived. Group the projects by `company-name`.

**Step 3: Check for recent contact in Chorus**

For each company, call `chorus-get-engagements` with `account-name.contains` set to the distinctive part of the company name and `date.from` set to today minus the quiet window. If no engagement comes back, call `chorus-get-emails` with `account-name.contains` set to the same text and `sent-time.from` set to the same date. Note the date of the most recent contact found, calling `chorus-get-engagements` again without the date filter and `max-records` 1 if needed.

**Step 4: Report**

A table of clients with no contact in the window, most troubled first: company, affected projects, lowest health score, number of late milestones, date of last Chorus contact (or "never recorded"), and the Chorus user who last spoke to them. Below it, one line naming the clients that are troubled but were contacted recently.

**Rules & Guidelines:**

* `teamwork-get-project-health`, `teamwork-get-milestones` and `teamwork-get-projects` are on the teamwork server. `chorus-get-engagements` and `chorus-get-emails` are on the chorus server.
* This prompt is read-only. Do not call `teamwork-create-message`, `teamwork-update-project`, `teamwork-create-risk` or any other teamwork write tool, and do not call any chorus write tool.

**Validation:**

* If no project is below the threshold and no milestone is late, say so and stop.
* If a company name is too generic to search Chorus reliably (a single common word), report it as unchecked rather than guessing.
* A Chorus account that matches several Teamwork companies should be reported against each, with a note.