Find Jira bugs whose Ghost Inspector tests now pass

**Objective:** Find the open bugs in Jira project {jira-project-key} that were raised from Ghost Inspector failures but whose test has passed consistently for the last {stable-days} days (default 7), and present them as close-out candidates. Nothing is closed here. A comment is posted only if {post-comments} is set to yes.

**Step 1: The candidate issues**

Call `jira-get-issue` on the jira server with `project-key` set to {jira-project-key} and `summary.contains` set to `Ghost Inspector failure`, `max-records` 100.

Discard any whose status is Done, Closed or Resolved. For each remaining issue keep its key, summary, status, assignee, creation date and updated date, and take the test name as the part of the summary after `Ghost Inspector failure: `.

If nothing is returned, report that no issue in the project follows the naming convention and stop.

**Step 2: Check the test on the other side**

For each candidate, call `ghost-inspector-get-test-result` on the ghost-inspector server with `test-name.contains` set to the test name and `date-created.from` set to the start of the stable window, `max-records` 50.

Classify the issue:

Close-out candidate, when there were at least three runs in the window and every one passed.
Still failing, when any run in the window failed. Record the most recent failing result id.
No evidence, when there were fewer than three runs, or the test name matched nothing in Ghost Inspector.

Never put an issue in the close-out list on the strength of a single passing run.

**Step 3: Comment, only if asked**

Do this step only when {post-comments} is yes, and only for issues in the close-out list.

For each one, call `jira-add-issue-comment` with `issue-id` set to the issue key and `body` set to a note beginning `Ghost Inspector verification run` and stating the number of consecutive passing runs, the window, and the most recent passing result id. If the key is rejected, call `jira-get-issue-watcher` with `issue-key` set to that key, read the issue id it returns, and retry once.

Before posting anything, show the user the list of issues that will receive a comment and ask for confirmation. Do not post without it.

**Step 4: Report**

Three tables. Close-out candidates: issue key, summary, assignee, runs in the window, all passing, most recent result id. Still failing: issue key, status, most recent failure date, failing result id. No evidence: issue key, summary, and which of the two reasons applies.

Finish with the counts, and state whether comments were posted.

**Rules & Guidelines:**

* `jira-get-issue`, `jira-add-issue-comment` and `jira-get-issue-watcher` are on the jira server. `ghost-inspector-get-test-result` is on the ghost-inspector server. All three servers must be connected.
* The linking convention used by every prompt on this server: a Jira issue raised from a Ghost Inspector failure has a summary beginning `Ghost Inspector failure: ` followed by the test name, and its first comment contains the line `Ghost Inspector result id: ` followed by the result id. Matching in both directions depends on this, so do not vary the wording. An issue that does not follow it will not be found by this prompt, which is worth saying in the report when the count looks low.
* Do NOT call `jira-update-issue` or `jira-assign-issue`. This prompt does not move an issue to Done under any circumstances, however clear the evidence looks.
* Do NOT call `ghost-inspector-execute-test` or `ghost-inspector-execute-suite`. Judge on runs that already happened; running the test now would only prove it passes once.

**Validation:**

* If a test name appears on two open issues, list both and mark them as possible duplicates rather than closing out either.
* If Ghost Inspector returns runs for a name that only partly matches, say so on the row and put the issue in the no evidence group.
* If {post-comments} is anything other than yes, post nothing and say in the report that comments were skipped.