Track a failed Ghost Inspector suite run in GitHub, once

**Objective:** Record the failed Ghost Inspector suite result `{suite-result-id}` as a GitHub issue, applying the label `{label}` if given, and link the issue back on the suite result.

**Step 1: Read the failure (Ghost Inspector)**

Call `ghost-inspector-get-suite-result` with `id` set to `{suite-result-id}`. If it is not found, report that and stop. If `passing` is true, say the run passed and stop.

Call `ghost-inspector-get-test-result` with `suite-id` set to the result's `suite-id`, `passing` set to false, and `date-created.from` / `date-created.to` set to the suite result's `date-execution-started` and `date-execution-finished`. For each failing test result, call `ghost-inspector-get-test-step` with `test-result-id` and `passing` false to get the failing step, and `ghost-inspector-get-console-log` with `test-result-id` and `error` true for console errors (keep the first three per test).

**Step 2: Look for an existing issue (GitHub)**

The issue title is `[Ghost Inspector] <suite-name> failing`. Call `github-get-issue` with `title.contains` set to `[Ghost Inspector] <suite-name>` and `status` open.

**Step 3: Draft, confirm, then write (GitHub)**

Draft the body in markdown: the suite name, the suite result id `{suite-result-id}`, the run time, pass/fail counts, then one section per failing test with its name, test id, test result id, the failing step's command, target and value, and the console errors.

Show the draft to the user and say whether you will create a new issue or comment on the existing one. Wait for confirmation.

* If an open issue exists: call `github-add-issue-comment` with its `issue-number` and the draft as `body`.
* Otherwise: call `github-add-issue` with the title, the draft as `body`, and `{label}` as `label` if given. It returns nothing, so call `github-get-issue` with `title.contains` again to get the new `issue-number` and `issue-url`.

**Step 4: Link back (Ghost Inspector)**

Call `ghost-inspector-add-suite-result-comment` with `suite-result-id` set to `{suite-result-id}` and a `message` of `Tracked in GitHub issue #<issue-number>: <issue-url>`.

**Step 5: Report**

The issue number and url, whether it was new or commented on, and the failing tests included.

**Rules & Guidelines:**

* The ghost-inspector tools are on the ghost-inspector server; the github tools are on the github server.
* Write at most once to each system: one `github-add-issue` or one `github-add-issue-comment`, then one `ghost-inspector-add-suite-result-comment`, and only after the user confirms the draft.
* Do NOT call `ghost-inspector-execute-suite`, `ghost-inspector-cancel-suite-run`, `github-update-issue` or `github-add-issue-assignee`.

**Validation:**

* If the suite result has failing counts but no failing test results in its time window, still file the issue with the suite-level counts and say the per-test detail could not be matched.
* If the new issue cannot be found again after creating it, do not create a second one. Report that the issue was created but could not be linked, and skip Step 4.