Service equipment before it fails and spot contract gaps

**Objective:** Build a preventive maintenance and warranty outreach list of installed equipment (office `{office-id}`, customer `{customer-name}`; defaults all) that has not been serviced in `{service-interval-days}` days (default 180) or whose warranty ends within 60 days.

Pass `{company}` as `company` on every call (if it is empty, omit `company` and the default company is used). Pass a generous `max-records` (1000). If a result comes back with exactly that many rows, say the result may be truncated.

**Step 1: Equipment**

Call `dynamics-gp-get-srv-equipment` with `office-id` and `customer-name.contains` when given. Keep active equipment (by `equipment-status`) where `last-service-date` is older than the interval or empty (use `install-date` for age then), or `warranty-end` falls within the next 60 days.

**Step 2: Contract coverage**

Per customer, call `dynamics-gp-get-srv-contract-line` by `customer-id` and match by `serial-number` or `equipment-id`. Mark each unit covered (with contract number and end date) or not covered.

**Step 3: Avoid duplicates**

Per customer, call `dynamics-gp-get-srv-service-call` by `customer-id` and drop units whose customer already has an open call (no `complete-date`) that mentions the unit's serial number or item.

**Step 4: Report**

Grouped by customer: item, serial number, asset tag, install date, last service date, days since service, warranty end, contract coverage. Covered units are maintenance to schedule; uncovered units are a contract sales opportunity. Say which is which.

**Rules & Guidelines:**

* This prompt is read-only. Do not call any tool whose name does not contain `get` (no add, update, note or email tools).
* Do not call `dynamics-gp-srv-service-call-add`; the separate `log-service-call` prompt creates calls.

**Validation:**

* If nothing is due, say so and give the next unit to fall due.