Verify a GitHub issue fix with a fresh Ghost Inspector run

**Objective:** Check whether the failure described in GitHub issue `{issue-number}` is fixed by re-running its Ghost Inspector test (`{test-id}` if given, otherwise the test named in the issue), and record the result on the issue.

**Step 1: Read the issue (GitHub)**

Call `github-get-issue` with `issue-number` set to `{issue-number}`, and `github-get-issue-comment` with the same `issue-number`. If the issue is not found, stop.

**Step 2: Identify the test (Ghost Inspector)**

* If `{test-id}` is given, call `ghost-inspector-get-test` with `id` set to it.
* Otherwise look in the issue title, body and comments for a Ghost Inspector test id or test name (issues filed from Ghost Inspector list each failing test's name and test id). Call `ghost-inspector-get-test` with `id`, or with `name.contains` set to the name.

If no test can be identified, or more than one matches, list what you found and stop so the user can supply `{test-id}`. If the issue names several tests, list them and ask whether to run all of them or one.

**Step 3: Confirm and run (Ghost Inspector)**

Tell the user which test you will run (name, suite, start url) and wait for confirmation. Call `ghost-inspector-execute-test` with `test-id` set to the test's id. Do not set `immediate`.

If it fails, call `ghost-inspector-get-test-step` with `test-result-id` set to the new result id and `passing` false to get the failing step.

**Step 4: Record it (GitHub)**

Call `github-add-issue-comment` with `issue-number` `{issue-number}` and a `body` stating the test name, the new result id, pass or fail, execution time, and the failing step's command and target if it failed.

**Step 5: Report**

Pass or fail, and if it passed, suggest the issue can be closed. Do not close it yourself.

**Rules & Guidelines:**

* The github tools are on the github server; the ghost-inspector tools are on the ghost-inspector server.
* Writes are exactly one `ghost-inspector-execute-test` per confirmed test and one `github-add-issue-comment`.
* Do NOT call `github-update-issue` (that would close or edit the issue), `ghost-inspector-accept-screenshot` or `ghost-inspector-update-test`.

**Validation:**

* If the issue is already closed, say so and ask whether to run the test anyway.
* A single pass after a history of intermittent failures is not proof of a fix. If the issue or its comments call the test flaky, say that one pass is weak evidence.