Turn a solved ServiceNow problem into a draft knowledge article

**Objective:** Draft a knowledge article in `{knowledge-base}` describing the symptom, cause and workaround of problem `{problem-number}`, linked to its configuration item.

**Step 1: Read the problem**

Call `servicenow-get-problem` with number `{problem-number}`. Keep short-description, configuration-item, known-error, state and resolution-code. A problem still in New or Assess has no cause to publish: stop and say so.

**Step 2: Avoid a duplicate**

Call `servicenow-get-knowledge` with short-description.contains set to key words from the problem and knowledge-base `{knowledge-base}`. If an article already covers it, show it and stop.

**Step 3: Gather the content**

Call `servicenow-get-problem-task` with problem `{problem-number}` for task short-descriptions and close codes. Ask the user for the cause and workaround text if they are not in the conversation already; this tool set does not return the problem's cause or workaround notes.

**Step 4: Draft and confirm**

Draft the article body in HTML with these sections: Symptoms, Cause, Workaround, Resolution (only if the problem is Resolved), Applies to (the configuration item). Propose short-description "<symptom> on <CI>", keywords from the symptom and CI, and article-type the tool lists for how-to or issue articles. Show the draft and ask for an explicit yes.

**Step 5: Write, in this order**

1. Call `servicenow-add-knowledge` once with knowledge-base `{knowledge-base}`, short-description, article-body and keywords. It is created as a draft; do not publish it.
2. Call `servicenow-get-knowledge` with short-description.contains set to the new short-description and workflow Draft to get its number and sys-id.
3. If the problem has a configuration-item, call `servicenow-add-knowledge-related-product` once with article set to the new sys-id and configuration-item set to the CI name.

**Step 6: Report**

The draft article number, its workflow state, and the linked CI. Remind the user it needs review before publishing.

**Rules & Guidelines:**

* Write tools allowed: `servicenow-add-knowledge` once and `servicenow-add-knowledge-related-product` once, after one confirmation. Do not call `servicenow-update-knowledge` to publish, and do not call `servicenow-update-problem`.
* If step 5.2 cannot find the draft, stop; never create a second article.