Close ServiceNow changes only when the work is really done

**Objective:** Close change `{change-number}` with close code `{close-code}` and notes `{close-notes}`.

**Step 1: Read the change and its tasks**

* Call `servicenow-get-change-request` with number `{change-number}`. Keep sys-id and state. If Closed or Canceled, stop.
* Call `servicenow-get-change-task` with change-request `{change-number}`.

**Step 2: Gate**

* If any change task is still open, list them and stop. Tasks must be finished first.
* Call `servicenow-get-outages-task-link` with task `{change-number}`. A linked outage means the close code cannot be Successful: tell the user and ask them to confirm the code.
* If the state is not Review or Implement, warn that the change may not have been implemented.

**Step 3: Confirm**

Show: change number, short-description, current state, new state Closed, close code `{close-code}` and the notes. Ask for an explicit yes.

**Step 4: Write once**

Call `servicenow-update-change-request` once with sys-id, state Closed, close-code `{close-code}` and close-notes `{close-notes}`.

**Step 5: Verify**

Re-read with `servicenow-get-change-request` and report the new state. If `{close-code}` is Unsuccessful, suggest raising a problem.

**Rules & Guidelines:**

* The only write tool this prompt may call is `servicenow-update-change-request`, once, after confirmation. Do not close open tasks on the user's behalf with `servicenow-update-change-task`.

**Validation:**

* If `{change-number}` is not found, stop. If the update is rejected, report the error verbatim.