Retest BugHerd bugs with Ghost Inspector and close them

**Objective:** Check whether task `{task-number}` in the BugHerd project `{project-name}` is fixed by running the Ghost Inspector tests that cover its page, and close it if they pass and the user agrees.

**Step 1: Read the task**

Call `bugherd-get-projects` with `name.contains` set to `{project-name}`. If nothing matches, say so and stop. If several match, list their names and project-id values and ask which one; do not guess. Then call `bugherd-get-tasks` with `project-id` and `task-number`. If it is not found, stop. Note its page, external-id and status.

**Step 2: Find the covering tests**

* If the external-id is "ghost-inspector:<test id>", that test covers it: call `ghost-inspector-get-test` with `id`.
* Otherwise call `ghost-inspector-get-test` with `max-records` 500 and keep tests whose start-url matches the task's page. Match pages by URL: compare host and path, ignoring the scheme, a leading "www.", a trailing slash, the query string and the fragment. A BugHerd project matches a Ghost Inspector suite when the suite start-url is on the project development-url host or one of its sites.
* If no test covers the page, say so and stop: this bug needs a manual retest.

**Step 3: Run them**

List the tests you will run and wait for an explicit yes. Then call `ghost-inspector-execute-test` once per test with `test-id` (and `immediate` false so the call waits for the result). Collect passing and execution-time.

**Step 4: Close the task if it passed**

If every test passed, propose: status done, and the comment "Retested with Ghost Inspector: <test names> passed on <date>." Wait for an explicit yes, then call `bugherd-update-task` once with `project-id`, `task-id` and `status` done, and `bugherd-add-comment` once.

If any test failed, call `ghost-inspector-get-test-step` with the new result's id and `passing` false and report the failed step; do not change the task.

**Step 5: Report**

Each test with its result, and what was changed in BugHerd.

**Rules & Guidelines:**

* Tools named bugherd-... are on the bugherd MCP server; tools named ghost-inspector-... are on the ghost-inspector MCP server. If either set of tools is missing, say which server is not connected and stop.
* The only write tools this prompt may call are `ghost-inspector-execute-test` (after the first confirmation), and `bugherd-update-task` and `bugherd-add-comment` (after the second).
* A passing test proves only what it checks; say so if the task describes something the test does not cover.

**Validation:**

* If a test run errors rather than failing, report it as inconclusive and leave the task alone.