Track each Bugsnag error with one linked Jira issue

**Objective:** Create a Jira issue in project {jira-project-key} for Bugsnag error {error-id}, but only if no issue already tracks it, and link the two records to each other. This prompt sets the linking convention every other prompt on this server relies on: the Jira issue summary ends with the Bugsnag error id, and the remote link's global id IS the Bugsnag error id.

**Step 1: Read the error (bugsnag server)**

Call `bugsnag-get-error` filtered by error-id {error-id}. Keep error-class, message, severity, status, events, users, last-seen-date, error-url and project-name. If nothing comes back, report that the error id does not exist in Bugsnag and stop.

**Step 2: Check it is not already tracked (jira server)**

Do both checks before writing anything.

* Call `jira-get-issue-remote-link` filtered by global-id {error-id}. A result means a Jira issue already links to this error.
* Call `jira-get-issue` filtered by project-key {jira-project-key} and summary containing {error-id}.

If either finds something, report the existing issue key or remote link title and stop. Do not create a duplicate.

**Step 3: Resolve the Jira target (jira server)**

* Call `jira-get-project` filtered by project-key {jira-project-key} and keep project-id. If there is no such project, stop and say so.
* Call `jira-get-issue-type` filtered by project-key {jira-project-key} and name {issue-type}. Keep issue-type-id. If that type does not exist in the project, list the available type names and stop.

**Step 4: Confirm, then create the issue (jira server)**

Show the user the summary you are about to create and wait for approval. Then call `jira-add-issue` once with the project-id and issue-type-id from step 3 and a summary in this exact shape:

error-class, then a colon, then the first line of the message, then a trailing marker of bugsnag: followed by {error-id} in square brackets.

`jira-add-issue` has no description parameter, so the detail goes in step 6.

**Step 5: Find the issue you just created (jira server)**

Call `jira-get-issue` filtered by project-key {jira-project-key} and summary containing {error-id}. Keep issue-key and the issue id. If it does not come back, report that the issue was created but could not be read back, and stop before the linking steps.

**Step 6: Add the detail as a comment (jira server)**

Call `jira-add-issue-comment` once against that issue id, with a body carrying: severity, status, event count, affected user count, first-seen and last-seen dates, and the Bugsnag error url from step 1.

**Step 7: Link the two systems**

* Call `jira-add-issue-remote-link` with the issue id, url set to the Bugsnag error url, title set to the error class, application-name set to Bugsnag, and global-id set to {error-id}. The global id is what makes this error findable later, so do not omit it or invent a different value.
* Only if {jira-site-url} was supplied: call `bugsnag-get-project` filtered by the project-name from step 1 to get project-id, then call `bugsnag-link-error-issue` with that project-id, {error-id}, and an issue-url of {jira-site-url} followed by /browse/ and the issue key. If {jira-site-url} is empty, skip this and tell the user the Bugsnag side was not linked back and why.

**Step 8: Report**

State the Jira issue key, the Bugsnag error id, and which of the two links were created.

**Rules & Guidelines:**

* `bugsnag-get-error`, `bugsnag-get-project` and `bugsnag-link-error-issue` are on the bugsnag server. `jira-get-issue`, `jira-get-project`, `jira-get-issue-type`, `jira-get-issue-remote-link`, `jira-add-issue`, `jira-add-issue-comment` and `jira-add-issue-remote-link` are on the jira server. All three servers must be connected.
* Create at most one Jira issue per run. Never retry `jira-add-issue` after a failure without re-running step 2 first.
* Do not change the error's state in Bugsnag. Do not call `bugsnag-fix-error`, `bugsnag-ignore-error`, `bugsnag-discard-error`, `bugsnag-assign-error` or `bugsnag-update-error-severity` here.
* Do not set the company parameter on the Bugsnag tools unless the user names a company.

**Validation:**

* If step 1 returns more than one error, list them and stop; the error id should be unique.
* If the Jira issue is created but step 5 finds nothing, do not create a second one. Report the partial state.
* If Bugsnag and Jira disagree about the project (the Bugsnag project-name has no obvious Jira counterpart), proceed anyway using {jira-project-key} as given, and say so in the report.