Keep GitHub error issues current with Bugsnag activity

**Objective:** Post a status comment on the GitHub issue for Bugsnag error `{error-id}` (issue `{issue-number}` if given, otherwise found by title) summarizing its recent activity 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 status, severity, events, users, last-seen-date, release-stages and error-url.

Call `bugsnag-get-event` with `error-id` set to `{error-id}`, `received.from` set to seven days before today, and `max-records` 100. From these, count occurrences per app-version and per app-release-stage, and note how many were unhandled.

**Step 2: Find the issue on GitHub**

If `{issue-number}` is given, call `github-get-issue` with `issue-number` set to it. Otherwise call `github-get-issue` with `title.contains` set to `{error-id}`. If none is found, stop and suggest the `file-github-issue-for-error` prompt. If several are found, list them and ask which to update.

Call `github-get-issue-comment` with the issue-number to read recent comments. If a comment from the last 24 hours already reports this error's activity, show it and ask before posting another.

**Step 3: Confirm and post**

Draft the comment:

* Bugsnag status and severity, total events and users
* Occurrences in the last seven days, by app-version and by release stage, and how many were unhandled
* Last seen date and the error-url

Show it, wait for an explicit yes, then call `github-add-issue-comment` once with `issue-number` and the comment as `body`.

**Rules & Guidelines:**

* `bugsnag-get-error` and `bugsnag-get-event` are on the bugsnag server. `github-get-issue`, `github-get-issue-comment` and `github-add-issue-comment` are on the github server.
* The only write tool this prompt may call is `github-add-issue-comment`, once, after confirmation. Do not call `github-update-issue`, `github-update-issue-comment`, or any Bugsnag Action tool such as `bugsnag-update-error-severity`.

**Validation:**

* If there were no events in the last seven days, say so in the comment rather than posting empty counts.
* If the issue is closed but the error is still being seen, point that out and ask whether to post anyway; a regression may need the issue reopened, which this prompt does not do.