Prove a Jira fix with a fresh Ghost Inspector run

**Objective:** Check whether the fix on Jira issue {issue-key} actually holds, by re-running the Ghost Inspector test that the issue was raised from and recording the outcome on the issue. This prompt runs a test and posts one comment. It does not change the issue's status.

**Step 1: Read the issue**

Call `jira-get-issue` on the jira server with `issue-key` set to {issue-key}. If nothing comes back, report that and stop. Keep the summary, status, assignee and project key.

**Step 2: Find the test**

Take the test name from the issue. If the summary begins `Ghost Inspector failure: `, the test name is the remainder. Otherwise, call `jira-get-issue-comment` with `issue-id` set to {issue-key} and look for a comment containing `Ghost Inspector result id: `; take the result id from it and call `ghost-inspector-get-test-result` on the ghost-inspector server with `id` set to that value to read the test name.

If {test-name} was supplied as a parameter, use that instead of either and say in the report that it was overridden.

Call `ghost-inspector-get-test` with `name.contains` set to the test name. If it matches no test, report that the issue cannot be verified automatically and stop. If it matches more than one, list the matches with their id, suite and browser, and stop rather than guessing which to run.

**Step 3: Run it**

Call `ghost-inspector-execute-test` with `test-id` set to the matched test's id. If {browser} was supplied, pass it as `browser`. Leave `immediate` unset so the run completes and the pass state is real.

Runs can take some time. Do not call the tool a second time because the first has not answered yet.

**Step 4: Gather detail if it failed**

If the run did not pass, call `ghost-inspector-get-test-step` with `test-result-id` set to the new run's id and `passing` set to false, and keep the first failing step. Also call `ghost-inspector-get-console-log` with the same `test-result-id` and `error` set to true, `max-records` 10.

**Step 5: Report back onto the issue**

Call `jira-add-issue-comment` with `issue-id` set to {issue-key} and `body` set to a verification note containing: whether the re-run passed; the new Ghost Inspector result id; the browser and execution time; and, when it failed, the failing step and the console errors. Begin the comment with `Ghost Inspector verification run` so later reads can recognise it.

If `jira-add-issue-comment` rejects the issue key, call `jira-get-issue-watcher` with `issue-key` set to {issue-key}, read the issue id it returns, and retry once.

**Step 6: Report**

State the issue key, the test that was run, whether it passed, the new result id, and whether the comment was posted. If it passed, say that the issue is a candidate to close but do not close it.

**Rules & Guidelines:**

* `jira-get-issue`, `jira-get-issue-comment`, `jira-add-issue-comment` and `jira-get-issue-watcher` are on the jira server. `ghost-inspector-get-test`, `ghost-inspector-get-test-result`, `ghost-inspector-execute-test`, `ghost-inspector-get-test-step` and `ghost-inspector-get-console-log` are 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.
* Do NOT call `jira-update-issue` or `jira-assign-issue`. Moving the issue to Done is a person's decision, and this prompt only supplies the evidence for it.
* Do NOT call `ghost-inspector-accept-screenshot`. A visual difference that the re-run reports is a finding, not something to sign off here.
* Do NOT call `ghost-inspector-execute-suite`. Run the one test, not everything around it.

**Validation:**

* If the test name cannot be determined from the summary, the comments or the {test-name} parameter, stop and say which of the three were tried.
* If `ghost-inspector-execute-test` returns no pass state, report the run as inconclusive and post no comment.
* If the issue is already Done, Closed or Resolved, say so and ask whether to proceed before running the test.