Find the ServiceNow article that already solves this incident

**Objective:** Find published knowledge that can help resolve incident `{incident-number}`.

**Step 1: Read the incident**

Call `servicenow-get-incident` with number `{incident-number}`. Keep sys-id, short-description, category and configuration-item.

**Step 2: Search in this order**

1. By product: if the incident has a configuration-item, call `servicenow-get-knowledge-related-product` with configuration-item set to it. Read each linked article with `servicenow-get-knowledge` by number.
2. By text: call `servicenow-get-knowledge` with short-description.contains set to two or three distinctive words from the incident, workflow Published. Try a second word set if the first finds nothing.
3. By known error: call `servicenow-get-problem` with short-description.contains using the same words and known-error true; search knowledge for that problem's short-description.
4. Related: for the best article so far, call `servicenow-get-related-article` with knowledge-article set to its number and read any related articles.

**Step 3: Rank**

Drop articles past valid-to. Rank by relevance to the symptom first, then rating, then view-count.

**Step 4: Report**

Up to five articles: number, short-description, why it matches, rating, link. Say plainly if none fits well.

**Step 5: Optional note**

Ask whether to add the top articles to the incident as a work note. Only after an explicit yes, call `servicenow-update-incident` once with the incident sys-id and work-notes listing the article numbers and titles.

**Rules & Guidelines:**

* The only write this prompt may make is the single `servicenow-update-incident` work note in Step 5, after a yes. Never change state, assignment or any other field, and do not call `servicenow-add-knowledge` or `servicenow-add-knowledge-feedback`.

**Validation:**

* If `{incident-number}` is not found, stop.