Turn Granola action items into tracked HubSpot tasks

**Objective:** Turn the action items and commitments from the Granola meeting whose title contains `{meeting-title}` into HubSpot tasks, linked to the matching contacts, company and deal. Items with no stated date are due `{due-in-days}` days after the meeting (default 3). Nothing is written until the user approves the list.

**Step 1: Meeting (Granola)**

Call `granola-get-note` with title.contains set to the meeting title. If several match, list them (id, title, created-at) and stop for the user to choose. If none match, say so and stop. Keep id, title, scheduled-start, created-at and summary.

**Step 2: Extract the action items (Granola)**

Read the action items, next steps and commitments from the summary. For each item, call `granola-get-transcript` with note-id set to the id and text.contains set to a distinctive word from the item, and keep the line that states it, with its speaker. Note who owns each item and any date mentioned.

**Step 3: Attendees and HubSpot records**

Call `granola-get-attendee` with note-id set to the id. For each attendee email, call `hubspot-get-contacts` with email set to that address (join on email, ignoring case) and keep record-id and company-id. For the matched company, call `hubspot-get-deals` with company-id and keep open deals; use a deal only when exactly one open deal clearly relates to the meeting, otherwise leave deal-ids empty and say so.

**Step 4: Check for existing tasks (HubSpot)**

For each item, call `hubspot-get-tasks` with contact-email set to the related attendee's email and task-title.contains set to a distinctive word from the item. Drop items that already have an open task and list them as "Already tracked".

**Step 5: Review**

Show a numbered table: subject, owner, due-date, priority (HIGH only when the meeting called it urgent, otherwise MEDIUM), type (CALL, EMAIL or TODO), associated contact, company and deal, and the transcript line it came from. Items owned by the customer become tasks phrased "Follow up with <name> on <item>". Ask which to create, by number, "all" or "none". Write nothing until the user answers.

**Step 6: Create the approved tasks**

For each approved item, call `hubspot-add-task` once with subject, body (the item, the quoted line, and "Source: Granola note <id>, <meeting date>"), due-date as an ISO date, status NOT_STARTED, priority, type, and contact-ids, company-ids and deal-ids as comma-separated record-ids. Report each returned id. Then call `hubspot-get-tasks` with task-title.contains set to each subject and confirm it exists.

**Rules & Guidelines:**

* `granola-get-note`, `granola-get-transcript` and `granola-get-attendee` are on the Granola server. `hubspot-get-contacts`, `hubspot-get-deals`, `hubspot-get-tasks` and `hubspot-add-task` are on the HubSpot server.
* The only write is `hubspot-add-task`, once per approved item. Call no other write tool: no other hubspot-add, hubspot-update, hubspot-rename, hubspot-remove, hubspot-subscribe, hubspot-unsubscribe or hubspot-import tool (including `hubspot-add-engagement-task` and `hubspot-update-task`). The Granola server is only read.
* Do not set owner-id unless the user gives a numeric HubSpot owner ID; put the owner's name in the body instead.
* Never invent an action item. Every task must trace to the summary or a transcript line.

**Validation:**

* If the meeting has no action items, say so and stop.
* If no attendee matches a HubSpot contact, still offer the tasks, linked to nothing, and say they will not appear on any record.
* If a create fails, report it and continue with the next item; do not retry it.