Keep HubSpot tasks in step with TickTick progress

**Objective:** Bring open HubSpot tasks assigned to `{assigned-to}` up to date with the TickTick project `{project-name}`: complete the ones finished in TickTick in the last `{lookback-days}` days (default 30), and move the due date or priority of the ones rescheduled there. Nothing is written until the user confirms.

**Step 1: Read HubSpot tasks**

Call `hubspot-get-tasks` (HubSpot server) with `assigned-to` set to the value. Drop tasks whose `task-status` is COMPLETED. Keep `record-id`, `task-title`, `due-date`, `priority`, `created-at`. If none remain, say so and stop.

**Step 2: Find the TickTick project**

Call `ticktick-get-projects` (TickTick server) with `name` set to the project name. If it does not match exactly one project, list the matches and stop. Keep `project-id`.

**Step 3: Match each HubSpot task in TickTick**

* Call `ticktick-get-completed-tasks` with `project-id`, `title.contains` set to the HubSpot task-title and `completed-time.from` set to today minus the lookback days. A task completed after the HubSpot created-at is **Done in TickTick**.
* Otherwise call `ticktick-get-tasks` with `project-id` and `title.contains` set to the task-title. A match whose `description` quotes the HubSpot record-id is a certain match; a title-only match is likely. If its `due-date` or priority differs from HubSpot, it is **Rescheduled in TickTick**.
* No match in either: **Not tracked**, leave it alone.

**Step 4: Confirm**

Show a numbered table: HubSpot task-title, HubSpot due-date and priority, TickTick status, completed-time or new due-date and priority (TickTick priority 5 is HIGH, 3 is MEDIUM, 1 is LOW and 0 is NONE in HubSpot), match certainty, and the proposed change (complete, or new due-date and priority). Ask which to apply, by number, "all" or "none". Write nothing until the user answers.

**Step 5: Update HubSpot**

For each approved row, call `hubspot-update-task` (HubSpot server) once with `id` set to the record-id and only the changed fields: `status` COMPLETED for Done rows, or `due-date` (ISO date) and `priority` for Rescheduled rows. Then call `hubspot-get-tasks` with `task-title` set to the task-title and `assigned-to` and confirm the new values.

**Rules & Guidelines:**

* `hubspot-get-tasks` and `hubspot-update-task` are on the HubSpot server; `ticktick-get-projects`, `ticktick-get-tasks` and `ticktick-get-completed-tasks` are on the TickTick server.
* The only write is `hubspot-update-task`, once per approved task. 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-update-engagement-task` and `hubspot-add-task`).
* TickTick is the source here and is only read. Never call a TickTick write tool (`ticktick-add-task`, `ticktick-update-task`, `ticktick-complete-task`, `ticktick-complete-tasks`, `ticktick-move-task`, `ticktick-assign-task`, `ticktick-unassign-task`, `ticktick-add-task-comment`, `ticktick-add-project`, `ticktick-update-project`, `ticktick-add-project-group`, `ticktick-update-project-group`, `ticktick-add-column`, `ticktick-update-column`, `ticktick-add-tag`, `ticktick-add-focus-session`).
* Never clear a HubSpot due-date because the TickTick task has none.

**Validation:**

* Matching is by title text unless the description quotes the record-id; mark title-only matches as likely and never apply them without the user seeing them.
* If several TickTick tasks match one HubSpot task, list them and skip that task.
* If an update fails, report it and continue; do not retry it.