Know which HubSpot tickets to work first

**Objective:** Rank the open HubSpot tickets (priority `{priority}`, owner `{ticket-owner}`, both default to all) and recommend the first `{max-tickets}` (default 25) to work.

**Step 1: Know which statuses are open**

Call `hubspot-get-ticket-pipelines`, then `hubspot-get-ticket-pipeline-stages` for each `pipeline-id`. Treat stages whose label means closed (Closed, Resolved, and similar) as closed; the rest are open.

**Step 2: Pull tickets**

Call `hubspot-get-tickets`, filtering by `priority` and `ticket-owner` when given. Keep tickets whose `ticket-status` matches an open stage (compare against both the stage-id and the label). Compute age in days from `create-date`.

**Step 3: Context for the top tickets**

Rank by priority (HIGH, MEDIUM, LOW, then blank) and then by age, oldest first. For the top `{max-tickets}`:

* Call `hubspot-get-notes` with `ticket-id` = the ticket's `record-id` to find the last update.
* Where `company-id` is set, call `hubspot-get-companies` with `record-id` to get the company name, and note if that company has other open tickets in the list.

**Step 4: Report**

Ranked table: rank, ticket, priority, status, category, age (days), days since last note, owner, company. Then call out: tickets with no owner, tickets with no note in 7 days, and companies with three or more open tickets.

**Rules & Guidelines:**

* This prompt is read-only. Do NOT call any write tool: `hubspot-add-contact`, `hubspot-add-company`, `hubspot-add-deal`, `hubspot-add-ticket`, `hubspot-update-contact`, `hubspot-update-company`, `hubspot-update-deal`, `hubspot-update-ticket`, `hubspot-add-contact-note`, `hubspot-add-company-note`, `hubspot-add-deal-note`, `hubspot-add-ticket-note`.

**Validation:**

* If no tickets are open, say so.
* If the stage list cannot be read, treat every ticket without a `close-date` as open and say you did.