Turn a Bugsnag error into one well documented GitHub issue

**Objective:** Open a GitHub issue for Bugsnag error `{error-id}`, labelled `{label}` (default: bug), and link it back to the error in Bugsnag.

**Step 1: Read the error in Bugsnag**

Call `bugsnag-get-error` with `error-id` set to `{error-id}`. If it returns nothing, say so and stop. Record error-class, message, severity, status, events, users, first-seen-date, last-seen-date, release-stages, context, project-name and error-url.

Call `bugsnag-get-event` with `error-id` set to `{error-id}` and `max-records` 5 to get the most recent occurrences: file, app-version, request-url, unhandled and received-at-date.

Call `bugsnag-get-project` with `name` set to the project-name to get the project-id, which the link step needs.

**Step 2: Check for an existing issue on GitHub**

Call `github-get-issue` with `title.contains` set to `{error-id}`. If an issue comes back, do not create another one: report it and go straight to Step 5 using its issue-url. Also call `github-get-issue` with `title.contains` set to the error-class, and if an open issue comes back, show it and ask whether it already covers this error before continuing.

**Step 3: Confirm**

Show the user the issue you will create:

* Title: `[Bugsnag {error-id}] <error-class>: <message, trimmed to 80 characters>`
* Label: `{label}` (default bug)
* Body: severity, status, events and users affected, first and last seen, release stages, the recent occurrences as a short list (app-version, file, request-url, unhandled), and the error-url.

Wait for an explicit yes before continuing.

**Step 4: Create the issue on GitHub**

Call `github-add-issue` once, with `title`, `body` and `label` as confirmed. It returns no fields, so call `github-get-issue` with `title.contains` set to `{error-id}` to read back the issue-number and issue-url.

**Step 5: Link it in Bugsnag**

Call `bugsnag-link-error-issue` once, with `error-id` set to `{error-id}`, `project-id` from Step 1 and `issue-url` from Step 4.

**Step 6: Report**

The issue number and URL, and whether the link in Bugsnag succeeded.

**Rules & Guidelines:**

* `bugsnag-get-error`, `bugsnag-get-event`, `bugsnag-get-project` and `bugsnag-link-error-issue` are on the bugsnag server. `github-get-issue` and `github-add-issue` are on the github server.
* The only write tools this prompt may call are `github-add-issue` (once, after confirmation) and `bugsnag-link-error-issue` (once). Do not call `bugsnag-create-error-issue`: it files through Bugsnag's own tracker integration and would create a second issue. Do not call `bugsnag-assign-error`, `bugsnag-fix-error` or `github-update-issue`.
* Keep the `[Bugsnag <error-id>]` prefix in the title. The other prompts on this server find issues by it.

**Validation:**

* If the issue was created but cannot be read back, report that it was created, do not create it again, and skip the link step.
* If the link step fails, report the issue URL so the user can link it by hand. Do not retry the issue creation.
* If the error is already fixed or discarded in Bugsnag, say so and ask before filing.