Fix, ignore or reopen Bugsnag errors deliberately

**Objective:** Apply the resolution `{resolution}` to the Bugsnag error `{error-id}` in project `{project-name}`, after confirming it is the right error and the right action. 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`. The write tools need the id, and `bugsnag-get-error` does not return one, so this step cannot be skipped. If more than one project matches, list them and stop.

**Step 2: Confirm the error**

Call `bugsnag-get-error` with `error-id` set to `{error-id}`. Show the user the error class, message, severity, status, users affected, events and last seen date, and state which action you are about to take. Wait for the user to confirm before writing anything.

**Step 3: Apply exactly one action**

Map `{resolution}` to a single call, passing the `project-id` from Step 1 and `error-id` `{error-id}`:

* fix, fixed or resolved: `bugsnag-fix-error`
* ignore or snooze: `bugsnag-ignore-error`
* discard: `bugsnag-discard-error`
* reopen or open: `bugsnag-open-error`

If `{resolution}` does not clearly map to one of those four, say so and stop without calling anything.

**Step 4: Confirm the result**

Call `bugsnag-get-error` again for `{error-id}` and report the status it now holds. If it is unchanged, say the write did not take effect rather than assuming it did.

**Rules & Guidelines:**

* Exactly one write call, and only after the user has confirmed. Never chain two resolutions.
* `bugsnag-discard-error` drops future occurrences as well as the current record. Warn the user of that before discarding and require an explicit yes.
* Do not call `bugsnag-update-error-severity`, `bugsnag-assign-error`, `bugsnag-update-project` or any project tool from this prompt.

**Validation:**

* If the error is already in the requested state, say so and make no call.
* If the project or the error cannot be resolved, stop before Step 3. Never write with a guessed id.