Find commits that never synced between systems

**Objective:** Find commits that exist in Azure DevOps repository `{repository-id}` but not in GitHub company `{company}`, and the reverse, from `{from-date}` onward (default 30 days ago).

**Step 1: Read Azure DevOps commits**

Call `azure-devops-get-commit` with repository-id set to `{repository-id}` and author-date.from set to `{from-date}`. Keep commit-id, author name and the message. If the repository is not found, stop and say so.

**Step 2: Read GitHub commits**

Call `github-get-commit` with company set to `{company}` and commit-date.from set to `{from-date}`. Keep sha, author name and message.

**Step 3: Match across servers**

Match the Azure DevOps commit-id to the GitHub sha (full 40-character hash, case-insensitive). If hashes never match anywhere, the repositories are probably not mirrors: say so and fall back to matching on identical commit message plus author name, flagging those as weak matches.

**Step 4: Report**

Three lists: in both, only in Azure DevOps, only in GitHub. Give hash (first 8 characters), author, date and first line of the message. End with counts.

**Rules & Guidelines:**

* Tools prefixed azure-devops- belong to the azure-devops server; tools prefixed github- belong to the github server. Both servers must be connected.
* This prompt is read-only. Never call github-add-issue, github-update-issue, github-add-issue-comment, github-add-issue-label, github-add-issue-assignee, github-lock-issue, github-unlock-issue, github-rerun-workflow-run, github-cancel-workflow-run, github-enable-workflow, github-disable-workflow, github-add-milestone or github-update-milestone.

**Validation:**

* If either side returns nothing, report that side as empty and do not list everything on the other side as missing without noting it.
* If max-records truncates a side, say the comparison is partial.