Resolve ServiceNow incidents with the right code and notes

**Objective:** Resolve incident `{incident-number}` with close code `{close-code}` and the resolution notes `{resolution-notes}`.

**Step 1: Read the incident**

Call `servicenow-get-incident` with number `{incident-number}`. Keep its sys-id, state, priority, assigned-to and short-description.

**Step 2: Check it can be resolved**

* If state is already Resolved or Closed, report that and stop.
* Call `servicenow-get-outages-task-link` with task `{incident-number}`. If an outage is linked, warn that the outage record should be closed too.
* If `{close-code}` is blank, list the close-code values the tool accepts and ask the user to pick one. ServiceNow will not resolve an incident without a close code and close notes.

**Step 3: Confirm**

Show the user: number, short-description, current state, the new state Resolved, the close code and the notes. Ask for an explicit yes.

**Step 4: Write once**

After a yes, call `servicenow-update-incident` once with sys-id from Step 1, state Resolved, close-code `{close-code}`, close-notes `{resolution-notes}`, and comments set to the same notes so the caller is told.

**Step 5: Verify**

Call `servicenow-get-incident` with number `{incident-number}` and confirm state is Resolved. Report the before and after state.

**Rules & Guidelines:**

* The only write tool this prompt may call is `servicenow-update-incident`, once, after confirmation. Do not call `servicenow-update-task-sla`, `servicenow-update-problem` or any add- tool.
* Resolve, do not Close. Closing is left to the auto-close rule or the caller.
* Never pass fields the user did not supply; the update only changes what it is given.

**Validation:**

* If `{incident-number}` is not found, stop.
* If the update returns an error, report it verbatim and do not retry with different values.