Confirm a Ghost Inspector fix with one deliberate rerun

**Objective:** Rerun the Ghost Inspector test named `{test-name}` and confirm whether a fix has taken effect, optionally overriding the starting url with `{start-url}` and the browser with `{browser}`.

**Step 1: Identify the test**

Call `ghost-inspector-get-test` with `name.contains` set to `{test-name}`. If more than one test matches, list the matches with their suite and id and stop; do not guess which one to run. Keep the `id`, and note its current `passing` state so you can say whether this rerun changes anything.

**Step 2: Show what is about to run and get agreement**

State the test name, its suite, the browser and region that will be used, and the starting url. Running a test performs real browser actions against a live site, which may create or change data there. Ask the user to confirm before continuing. Do not proceed without an explicit yes.

**Step 3: Run it, once**

Call `ghost-inspector-execute-test` with `test-id` from step 1, plus `start-url` and `browser` only if those parameters were supplied. Do not set `immediate`, because this prompt exists to report the outcome and `immediate` returns before there is one. Call this tool exactly once. If it fails to return a result, report that and stop; do not retry.

**Step 4: Report the outcome**

If `passing` is true, report that the test now passes, with the execution time, and compare that time against the test's previous state from step 1.

If `passing` is false, diagnose it before reporting. Call `ghost-inspector-get-test-result` with the `test-id` and `passing` false to find the run you just made, take its `id`, then call `ghost-inspector-get-test-step` with that `test-result-id` and `passing` false, and `ghost-inspector-get-console-log` with the same `test-result-id` and `error` true. Report the failing step, its command and target, and any related console errors.

**Rules and guidelines:**

* `ghost-inspector-execute-test` is the ONLY tool in this prompt that may change anything, and it may be called once, after the confirmation in step 2.
* Do NOT call `ghost-inspector-execute-suite`, `ghost-inspector-update-test`, `ghost-inspector-duplicate-test`, `ghost-inspector-execute-on-demand-test` or any create tool.
* Do not rerun a failing test hoping for a different answer. One run, then report.

**Validation:**

* If `{test-name}` matches nothing, say so and list some test names from `ghost-inspector-get-test`.
* If the user declines the confirmation, stop without running anything.