Open HubSpot tickets in the right queue, without duplicates

**Objective:** Open a HubSpot ticket "{subject}" describing `{description}`, priority `{priority}` (default MEDIUM), for `{company-name}` when given.

**Step 1: Check for duplicates**

If `{company-name}` is given, call `hubspot-get-companies` with `company-name.contains` to get the record-id (stop if several match), then `hubspot-get-tickets` with `company-id` = it. Show any open ticket with a similar subject and ask whether to continue.

**Step 2: Resolve pipeline and status**

Call `hubspot-get-ticket-pipelines` and take the pipeline with the lowest `display-order` unless the user named one. Call `hubspot-get-ticket-pipeline-stages` with its `pipeline-id` and take the stage with the lowest `display-order` (normally New).

**Step 3: Confirm**

Show subject, description, priority, pipeline label, status label, and the ids you will send. Wait for an explicit yes.

**Step 4: Create**

Call `hubspot-add-ticket` once with `subject`, `description`, `priority`, `pipeline` = the pipeline-id and `ticket-status` = the stage-id. If a company was resolved, call `hubspot-add-ticket-note` once with the new ticket id and `note` = "Reported by <company name> (company ID <id>)."

**Step 5: Verify and report**

Call `hubspot-get-tickets` with `record-id` = the new id and report it. Say that `hubspot-add-ticket` does not associate the ticket with the company, so it should be linked in HubSpot.

**Rules & Guidelines:**

* Only `hubspot-add-ticket` and `hubspot-add-ticket-note` may write, each once, after confirmation.
* Do NOT call any other write tool: `hubspot-add-contact`, `hubspot-add-company`, `hubspot-add-deal`, `hubspot-update-contact`, `hubspot-update-company`, `hubspot-update-deal`, `hubspot-update-ticket`, `hubspot-add-contact-note`, `hubspot-add-company-note`, `hubspot-add-deal-note`.
* Do not set `owner-id`. No tool maps a person's name to a HubSpot owner ID, so leave ownership unchanged unless the user gives you a numeric owner ID.

**Validation:**

* Never send a status label as `ticket-status`; always the stage-id.
* If the create fails, report the error and do not add the note.