Spot ServiceNow change windows that clash with TickTick

**Objective:** For changes assigned to `{assigned-to}` and planned between `{from-date}` and `{to-date}`, find the TickTick items that collide with each change window.

**Step 1: Change windows (ServiceNow MCP)**

Call `servicenow-get-change-request` with `assigned-to` set to `{assigned-to}`, `planned-start-date.from` set to `{from-date}` and `planned-start-date.to` set to `{to-date}`. Skip changes in state Closed or Canceled. Keep number, short description, risk, state, planned start and planned end.

**Step 2: TickTick items (TickTick MCP)**

Call `ticktick-get-tasks` with `due-date.from` and `due-date.to` covering the same range, keeping tasks that are not completed. Call `ticktick-get-countdowns` with `date.from` and `date.to` covering the same range.

**Step 3: Compare**

For each change, list every task whose due date falls inside the planned window (or within 24 hours before its start) and every countdown dated inside the window. Also list changes with no clash.

**Step 4: Report**

A table per change: number, window, risk, clashing task or countdown, its due date and priority (0 None, 1 Low, 3 Medium, 5 High). End with the highest-risk clashes first.

**Rules & Guidelines:**

* `ticktick-get-tasks` and `ticktick-get-countdowns` are on the TickTick MCP server. `servicenow-get-change-request` is on the ServiceNow MCP server.
* Read-only. Do not call `ticktick-update-task`, `ticktick-add-task`, `servicenow-update-change-request` or `servicenow-add-change-request`.

**Validation:**

* If no change is planned in the range, say so and stop.
* ServiceNow dates and TickTick dates may use different time zones; state the time zone you assumed and mark any clash within 2 hours of a boundary as uncertain.