Verify many issues with bounded concurrent fan-out of the single-issue
fetchIssueVerification.
This is a deliberately thin worker pool, NOT one aliased GraphQL query:
per-issue timeline cursors make aliasing unmanageable, and all-or-nothing
failure (one bad issue poisoning the batch) is exactly what we want to
avoid. No retry layer is added here — octokit is expected to be a
ThrottledOctokit whose backoff already covers secondary rate limits.
Verify many issues with bounded concurrent fan-out of the single-issue fetchIssueVerification.
This is a deliberately thin worker pool, NOT one aliased GraphQL query: per-issue timeline cursors make aliasing unmanageable, and all-or-nothing failure (one bad issue poisoning the batch) is exactly what we want to avoid. No retry layer is added here —
octokitis expected to be a ThrottledOctokit whose backoff already covers secondary rate limits.