Decide what to do with every overdue Pipedrive activity

**Objective:** Triage the open activities that are overdue by up to `{lookback-days}` days (default 30), optionally only those assigned to `{user-name}`, and recommend what to do with each.

**Step 1: Resolve the user (optional)**

If `{user-name}` is given, call `pipedrive-get-user` with `name.contains`. If more than one user matches, list them and stop. Keep the user-id.

**Step 2: Pull the overdue activities**

Call `pipedrive-get-activity` with `done` = false, `due-date.from` = today minus the lookback, `due-date.to` = yesterday, and `assigned-to-user-id` if resolved.

**Step 3: Weigh them**

Activities return the deal title, not its ID. For the 20 activities with a deal-title, call `pipedrive-get-deal` with `title.contains` and `status` = open to get the deal's value and stage. An activity linked to a deal that is no longer open is a candidate to drop.

Rank by: linked to an open deal first, then deal value, then type (deadline and meeting before call, email and task), then days overdue.

**Step 4: Report**

1. **Summary:** overdue count per assignee and per type.
2. **Ranked table:** subject, type, due date, days overdue, deal, deal value, contact, assignee, recommendation.
3. Recommendations are one of: **Do today** (open deal, under 7 days overdue), **Reschedule** (still relevant), **Drop** (deal closed, or over 21 days overdue with nothing to show it still matters).

**Rules & Guidelines:**

* Read-only. Do not call `pipedrive-update-activity` or `pipedrive-add-activity`. To move the dates, the user can run the reschedule-overdue-activities prompt.
* Do not recommend dropping a meeting without saying who else is affected (contact-person-name).

**Validation:**

* If nothing is overdue, say so and stop.