Raise one clear tracker issue for each Bugsnag error

**Objective:** Raise a tracker issue for the Bugsnag error `{error-id}` in project `{project-name}`, with a title and description worth reading. This prompt changes data.

**Step 1: Resolve the project id**

Call `bugsnag-get-project` with `name` set to `{project-name}` and keep its `project-id`.

**Step 2: Gather the detail**

Call `bugsnag-get-error` for `{error-id}`, then `bugsnag-get-event` with `error-id` set to `{error-id}` and `max-records` set to 10. From those, establish the error class and message, how many users are affected, which app versions and release stages it occurs in, whether it is unhandled, the file or context it happens in, and the `error-url`.

**Step 3: Write the issue title**

Use `{issue-title}` if one was given. Otherwise write one: the error class, the failing context, and the impact in a few words, for example "TypeError in checkout submit, 240 users since 4.2.1". Show the user the title and wait for confirmation.

**Step 4: Create the issue**

Call `bugsnag-create-error-issue` with the `project-id` from Step 1, `error-id` `{error-id}` and the confirmed `issue-title`. Then report the result along with the `error-url` so the user can follow it.

**Rules & Guidelines:**

* One issue per error. Check first whether an issue already exists for it and stop if it does.
* Do not call `bugsnag-link-error-issue` from this prompt; linking an existing issue is a different job.
* Do not mark the error fixed or assign it while raising the issue.

**Validation:**

* If the project has no linked issue tracker, the create will fail. Report that plainly rather than retrying.
* If the error cannot be read, stop before Step 4 rather than raising an issue against a guessed id.