Context

The automated spec-sync job opens a weekly PR that copies JSON test files from mongodb/specifications into the driver. The PR body lists which local spec directories changed, but not which upstream spec PRs those changes come from. Reviewers cannot see which upstream changes they are approving.

Definition of done

The spec-sync PR body includes a section that lists the merged PRs in mongodb/specifications since the last spec-sync PR was merged. Each entry links to the upstream PR and to the JIRA ticket named in its title. The sync still completes when the GitHub API is unavailable.

Pitfalls

The last-sync date comes from a git log grep for prior sync commit subjects; the pattern must require a date so it does not match commits that only mention the sync scripts. The GitHub Search API call runs before the token bootstrap, so it uses unauthenticated requests (or GITHUB_TOKEN if set) and must not abort the sync on failure.

Implementation plan: gist