Tell Jira issues when their GitHub build fails

**Objective:** Find the failed GitHub Actions runs in repository `{repository}` (if blank, use the connector's default repository) from the last `{lookback-days}` days (default 3), match each to a Jira issue in project `{project-key}`, and post the failure as a comment on that issue after the user confirms.

**Step 1: Read the failures**

Call `github-get-workflow-run` with `conclusion` = failure, `created-date.from` = today minus `{lookback-days}` days and `max-records` 50 (pass `company` = `{repository}` when given). If nothing comes back, report no failures and stop. Keep only the newest failed run per branch.

**Step 2: Find the Jira key**

For each run, look for a `{project-key}` key (uppercase, hyphen, number, for example ABC-123) in the branch first, then the commit-message. A run with no key goes in the unmatched list.

**Step 3: Resolve the Jira issue**

For each key, call `jira-get-issue` with `issue-key` set to it. If it does not exist, move the run to the unmatched list. Otherwise call `jira-get-issue-watcher` with `issue-key` set to it to get `issue-id`; if no row comes back, move it to the unmatched list with the reason no issue id.

Skip any issue whose status is Done or another closed status, and say so.

**Step 4: Confirm**

List each proposed comment (Jira key, workflow name, branch, run url) and the unmatched runs. Wait for an explicit yes.

**Step 5: Write**

For each confirmed issue, call `jira-add-issue-comment` once with `issue-id` and a body naming the workflow, the branch, the run-number, the short sha, the commit author and the run url.

**Step 6: Report**

Comments posted, and the unmatched runs with their reason.

**Rules & Guidelines:**

* `github-get-workflow-run` is on the github server; Tools whose names start with jira- are on the jira server.
* The only write is `jira-add-issue-comment`, at most one per Jira issue per run. Do NOT call `github-rerun-workflow-run`, `github-cancel-workflow-run` or `jira-update-issue`.

**Validation:**

* Before commenting, call `jira-get-issue-comment` with that `issue-id` and skip the issue if a comment already contains the run url, so a rerun of this prompt does not post twice.
* If a branch and its commit message name different keys, use the branch key and mention the other in the comment.