Copy labelled GitHub issues to Jira exactly once

**Objective:** For every open GitHub issue in repository `{repository}` (if blank, use the connector's default repository) carrying label `{label}`, make sure a linked Jira issue exists in project `{project-key}`, creating the missing ones after the user confirms.

**Step 1: List the GitHub issues**

Call `github-get-issue` with `labels.contains` = `{label}`, `status` = open and `max-records` 50 (pass `company` = `{repository}` when given). If nothing comes back, report that and stop.

**Step 2: Find the gap**

Call `jira-get-issue-remote-link` with `application-name` = GitHub once, and collect every `global-id`. A GitHub issue whose issue-url is in that set is already synced. The rest are the gap.

**Step 3: Confirm**

List the gap (number, title, issue-url) and the already-synced count. Resolve `project-id` with `jira-get-project` (`project-key` = `{project-key}`) and the Bug `issue-type-id` with `jira-get-issue-type` (`project-key` = `{project-key}`, `name` = Bug). Wait for an explicit yes, or a subset of numbers, before writing anything.

**Step 4: Write, one issue at a time**

For each confirmed GitHub issue:

1. `jira-add-issue` with `project-id`, `issue-type-id` and `summary` set to the title followed by (GitHub #number).
2. Take the new key and id from the response; if the id is missing, call `jira-get-issue-watcher` with `issue-key` set to the new key.
3. `jira-add-issue-remote-link` with `url` and `global-id` both set to the issue-url, `title` the GitHub title, `application-name` GitHub.
4. `github-add-issue-comment` on that number: Tracked in Jira as the new key.

If any call fails, stop the loop and report where it stopped.

**Step 5: Report**

A table: GitHub number, Jira key, link created (yes/no), comment posted (yes/no).

**Rules & Guidelines:**

* Tools whose names start with jira- are on the jira server; tools whose names start with github- are on the github server.
* Create at most 20 Jira issues in one run; ask before continuing past 20.
* Do NOT call `github-update-issue`, `jira-assign-issue` or `jira-update-issue`.

**Validation:**

* The remote link's `global-id` is the dedupe key. If a link cannot be created, warn that a rerun will create a duplicate Jira issue for that GitHub issue.
* If `jira-get-issue-remote-link` fails, stop: without it there is no way to avoid duplicates.