@gitkraken/core-gitlens 0.5.116 → 0.7.0

package/src/plus/integrations/providers/models.ts

@@ -1,1816 +0,0 @@
-import type {
-	Account,
-	ActionablePullRequest,
-	AnyEntityIdentifierInput,
-	AzureDevOps,
-	AzureOrganization,
-	AzureProject,
-	AzureSetPullRequestInput,
-	Bitbucket,
-	BitbucketServer,
-	BitbucketWorkspaceStub,
-	CollectionMetadata,
-	CursorPageInput,
-	EnterpriseOptions,
-	GetRepoInput,
-	GitBuildStatus,
-	GitBuildStatusState as GitBuildStatusStateType,
-	GitHub,
-	GitHubPullRequestFieldMap,
-	GitIssueState as GitIssueStateType,
-	GitLab,
-	GitLabGroup,
-	GitMergeStrategy,
-	GitPullRequest,
-	GitPullRequestMergeableState as GitPullRequestMergeableStateType,
-	GitPullRequestReviewState as GitPullRequestReviewStateType,
-	GitPullRequestState as GitPullRequestStateType,
-	GitRepository,
-	GitRepositoryRemoteInfo,
-	Jira,
-	JiraProject,
-	JiraResource,
-	Linear,
-	LinearOrganization,
-	LinearTeam,
-	NumberedPageInput,
-	Organization,
-	Issue as ProviderApiIssue,
-	PullRequestWithUniqueID,
-	RequestFunction,
-	RequestOptions,
-	Response,
-	SetPullRequestInput,
-	Trello,
-} from '@gitkraken/provider-apis';
-import { EntityIdentifierUtils } from '@gitkraken/provider-apis/entity-identifiers';
-import { GitProviderUtils } from '@gitkraken/provider-apis/provider-utils';
-import { githubSearchResultLimit } from '../../git-github/api/config.js';
-import type { Account as UserAccount } from '../../../git/models/author.js';
-import type { IssueProject, IssueShape, IssueStateFilter } from '../../../git/models/issue.js';
-import { Issue, RepositoryAccessLevel } from '../../../git/models/issue.js';
-import type {
-	PullRequestRef,
-	PullRequestRefs,
-	PullRequestRepositoryIdentityDescriptor,
-	PullRequestState,
-	PullRequestStateFilter,
-} from '../../../git/models/pullRequest.js';
-import {
-	PullRequest,
-	PullRequestMergeableState,
-	PullRequestStatusCheckRollupState,
-} from '../../../git/models/pullRequest.js';
-import type { Provider, ProviderReference } from '../../../git/models/remoteProvider.js';
-import type { ProviderScope } from '../../../git/models/resourceDescriptor.js';
-import { gitSuffixRegex } from '../../../git/utils/remote.utils.js';
-import type { PagedResult } from '../../../utils/paging.js';
-import { equalsIgnoreCase } from '../../../utils/string.js';
-import type { IntegrationIds } from '../constants.js';
-import {
-	GitCloudHostIntegrationId,
-	GitSelfManagedHostIntegrationId,
-	IssuesCloudHostIntegrationId,
-} from '../constants.js';
-import type { Integration, IntegrationType } from '../models/integration.js';
-import type {
-	IssueSearchCapabilities,
-	IssueSorting,
-	PullRequestSearchCapabilities,
-	PullRequestSorting,
-} from '../providerFilters.js';
-import { IssueFilter, PullRequestFilter } from '../providerFilters.js';
-
-export { IssueFilter, PullRequestFilter } from '../providerFilters.js';
-export type {
-	IssueSearchCapabilities,
-	IssueSearchCriteria,
-	IssueSearchRelationship,
-	IssueSortField,
-	IssueSorting,
-	PullRequestSearchCapabilities,
-	PullRequestSearchCriteria,
-	PullRequestSortField,
-	PullRequestSorting,
-} from '../providerFilters.js';
-import type { ProviderRepositoryShape } from '../results.js';
-
-export type { ProviderOrganization, ProviderRepositoryShape } from '../results.js';
-import { fromProviderAccount, toProviderAccount } from './accounts.js';
-import {
-	azureAccountWideIssueSorts,
-	azureIssueSorts,
-	githubAccountWideIssueSorts,
-	githubIssueSorts,
-	gitlabAccountWideIssueSorts,
-	gitlabIssueSorts,
-	jiraIssueSorts,
-	linearIssueSorts,
-	trelloIssueSorts,
-} from './issueSorts.js';
-import type { ProviderPullRequestReview, ProviderPullRequestReviews } from './pullRequestReviews.js';
-import {
-	fromPullRequestReviewDecision,
-	providerPullRequestReviewStateDismissed,
-	toCompletedReviews,
-	toProviderReviewDecision,
-	toProviderReviews,
-	toReviewRequests,
-} from './pullRequestReviews.js';
-import { getEntityIdentifierInput } from './utils.js';
-
-type GitBuildStatusState = GitBuildStatusStateType;
-type GitIssueState = GitIssueStateType;
-type GitPullRequestMergeableState = GitPullRequestMergeableStateType;
-type GitPullRequestReviewState = GitPullRequestReviewStateType;
-type GitPullRequestState = GitPullRequestStateType;
-
-// Local runtime copies of the `@gitkraken/provider-apis` string enums. Duplicated (not imported as
-// values) because the SDK ships as CJS whose named enum exports can't be statically imported as ESM
-// values from the bundled `dist`. Exported so the enum-parity test can deep-equal them against the
-// real SDK enums and turn any upstream drift into a test failure instead of a silent mismatch.
-export const GitBuildStatusState = {
-	ActionRequired: 'ACTION_REQUIRED' as GitBuildStatusState,
-	Cancelled: 'CANCELLED' as GitBuildStatusState,
-	Error: 'ERROR' as GitBuildStatusState,
-	Failed: 'FAILED' as GitBuildStatusState,
-	Pending: 'PENDING' as GitBuildStatusState,
-	Running: 'RUNNING' as GitBuildStatusState,
-	Skipped: 'SKIPPED' as GitBuildStatusState,
-	Success: 'SUCCESS' as GitBuildStatusState,
-	Warning: 'WARNING' as GitBuildStatusState,
-	OptionalActionRequired: 'OPTIONAL_ACTION_REQUIRED' as GitBuildStatusState,
-} as const;
-
-export const GitIssueState = {
-	Open: 'OPEN' as GitIssueState,
-	Closed: 'CLOSED' as GitIssueState,
-} as const;
-
-export const GitPullRequestState = {
-	Open: 'OPEN' as GitPullRequestState,
-	Closed: 'CLOSED' as GitPullRequestState,
-	Merged: 'MERGED' as GitPullRequestState,
-} as const;
-
-export const GitPullRequestReviewState = {
-	Approved: 'APPROVED' as GitPullRequestReviewState,
-	ChangesRequested: 'CHANGES_REQUESTED' as GitPullRequestReviewState,
-	Commented: 'COMMENTED' as GitPullRequestReviewState,
-	ReviewRequested: 'REVIEW_REQUESTED' as GitPullRequestReviewState,
-} as const;
-
-export const GitPullRequestMergeableState = {
-	Behind: 'BEHIND' as GitPullRequestMergeableState,
-	Blocked: 'BLOCKED' as GitPullRequestMergeableState,
-	Conflicts: 'CONFLICTS' as GitPullRequestMergeableState,
-	FailingChecks: 'FAILING_CHECKS' as GitPullRequestMergeableState,
-	Mergeable: 'MERGEABLE' as GitPullRequestMergeableState,
-	Unknown: 'UNKNOWN' as GitPullRequestMergeableState,
-	UnknownAndBlocked: 'UNKNOWN_AND_BLOCKED' as GitPullRequestMergeableState,
-	Unstable: 'UNSTABLE' as GitPullRequestMergeableState,
-} as const;
-
-/**
- * Forward-only host type — the package only sets `EnrichablePullRequest.enrichable`
- * for the host to consume. Typed as `any` to avoid duplicating the host's
- * `EnrichableItem` shape.
- */
-type EnrichableItem = any;
-
-export type ProviderAccount = Account;
-export type ProviderReposInput = (string | number)[] | GetRepoInput[];
-export type ProviderRepoInput = GetRepoInput;
-
-/**
- * Which half of {@link ProviderReposInput} a caller supplied: repository IDS rather than descriptors.
- *
- * The union has no discriminant, so the answer is the element shape — and several layers need it for different
- * reasons (`ProvidersApi` to pick `repoIds` vs `repos` in the SDK input, `GitHostIntegration` to refuse an
- * id-based read a provider can't serve, `listIssuesPage` to know GitLab's id form takes the SDK's own merging
- * aggregate). One predicate rather than one per layer, because each copy is free to disagree about the shape,
- * and the symptom of disagreement is a read routed to the wrong provider query.
- *
- * Takes `unknown` rather than {@link ProviderReposInput} because `ProvidersApi.isRepoIdsInput` forwards here and
- * is public with an unvalidated parameter, so the array check has to stay part of the rule rather than be assumed
- * from the parameter type.
- */
-export function isRepoIdsInput(input: unknown): input is (string | number)[] {
-	return (
-		input != null &&
-		Array.isArray(input) &&
-		input.every(repo => typeof repo === 'string' || typeof repo === 'number')
-	);
-}
-
-export type ProviderPullRequest = Omit<GitPullRequest, 'reviews'> & { reviews: ProviderPullRequestReviews };
-export type ProviderRepository = GitRepository;
-export type ProviderIssue = ProviderApiIssue;
-export type ProviderEnterpriseOptions = EnterpriseOptions;
-export type ProviderJiraProject = JiraProject;
-export type ProviderJiraResource = JiraResource;
-export type ProviderLinearTeam = LinearTeam;
-export type ProviderLinearOrganization = LinearOrganization;
-export type ProviderAzureProject = AzureProject;
-export type ProviderAzureResource = AzureOrganization;
-export type ProviderBitbucketResource = BitbucketWorkspaceStub;
-export type ProviderGitHubOrganization = Organization;
-export type ProviderGitLabGroup = GitLabGroup;
-
-/**
- * Returns an account-wide PR identity. Provider PR ids are commonly scoped to a repository or organization,
- * so an id alone is never safe for deduplication across a multi-repository fan-out. Repository identity wins
- * when available so the same row still deduplicates when a later facet adds or removes its URL.
- */
-export function getProviderPullRequestIdentity(
-	pr: Pick<ProviderPullRequest, 'id' | 'repository' | 'url'>,
-): string | undefined {
-	const repository = pr.repository as
-		| {
-				id?: string | number;
-				name?: string;
-				namespace?: string;
-				owner?: { login?: string } | string;
-				project?: string;
-		  }
-		| undefined;
-	const urlIdentity = pr.url != null && pr.url.trim() !== '' ? `url:${pr.url}` : undefined;
-	if (repository == null) return urlIdentity;
-
-	const owner = typeof repository.owner === 'string' ? repository.owner : repository.owner?.login;
-	const repositoryId = repository.id != null ? String(repository.id).trim() : '';
-	if (repositoryId !== '') return `repository:${repositoryId}:pull-request:${pr.id}`;
-
-	const name = repository.name?.trim() ?? '';
-	const namespace = (repository.namespace ?? owner)?.trim() ?? '';
-	const project = repository.project?.trim() ?? '';
-	if (name !== '' && (namespace !== '' || project !== '')) {
-		return `repository:${namespace}/${project}/${name}:pull-request:${pr.id}`;
-	}
-	return urlIdentity;
-}
-
-export type ProviderHierarchyResult<T> = PagedResult<T> & {
-	readonly truncated?: boolean;
-	/**
-	 * SDK collection metadata merged across the drained pages. Independent from the local `truncated` backstop:
-	 * a page-drain backstop stays visible even if every fetched page reported `complete`, and SDK
-	 * incompleteness is preserved even when the drain finished within its page budget.
-	 */
-	readonly metadata?: CollectionMetadata;
-};
-
-/**
- * A normalized {@link PagedResult} that additionally carries the SDK's collection {@link CollectionMetadata}
- * (completeness + per-scope failures). Named to avoid colliding with the public ProviderBackend
- * `ProviderPagedResult` in `results.ts`: this is the integration-local carrier between the `ProvidersApi`
- * boundary and the code that maps metadata into warnings/truncation. `metadata` is optional so providers and
- * test doubles that predate the SDK metadata contract keep behaving exactly as before.
- */
-export type ProviderApiPagedResult<T> = PagedResult<T> & {
-	readonly metadata?: CollectionMetadata;
-};
-
-/**
- * A non-paged collection result carrying SDK {@link CollectionMetadata}. Used for fan-out reads that return a
- * flat set of values with completeness/failure metadata but no provider-native pagination (e.g. Jira project
- * discovery across resources, Trello board search).
- */
-export type ProviderApiCollectionResult<T> = {
-	readonly values: NonNullable<T>[];
-	readonly metadata?: CollectionMetadata;
-};
-
-export const ProviderPullRequestReviewState = GitPullRequestReviewState;
-export const ProviderBuildStatusState = GitBuildStatusState;
-export type ProviderRequestFunction = RequestFunction;
-export type ProviderRequestResponse<T> = Response<T>;
-export type ProviderRequestOptions = RequestOptions;
-
-export enum PagingMode {
-	Project = 'project',
-	Repo = 'repo',
-	Repos = 'repos',
-}
-
-export interface PagingInput {
-	cursor?: string | null;
-	page?: number;
-}
-
-export interface PagedRepoInput {
-	repo: GetRepoInput;
-	cursor?: string;
-}
-
-export interface PagedProjectInput {
-	namespace: string;
-	project: string;
-	cursor?: string;
-}
-
-export interface GetPullRequestsOptions {
-	authorLogin?: string;
-	assigneeLogins?: string[];
-	reviewRequestedLogin?: string;
-	// Reviewer filters keyed differently per provider: GitHub/GitLab use reviewRequestedLogin (login),
-	// Bitbucket/Azure DevOps use reviewerId (account id), Bitbucket Server uses reviewerLogin (login).
-	reviewerId?: string;
-	reviewerLogin?: string;
-	mentionLogin?: string;
-	// PR states to include; when omitted the provider returns its default (open only).
-	states?: GitPullRequestState[];
-	query?: string;
-	cursor?: string; // stringified JSON object of type { type: 'cursor' | 'page'; value: string | number } | {}
-	baseUrl?: string;
-	// 1-based page to request from numbered-page providers; takes precedence over a page-typed cursor.
-	page?: number;
-	// Items to request per page (numbered-page providers, plus GitHub's maxPageSize).
-	pageSize?: number;
-	// Opt in to repository remote metadata (clone URLs) when the PR payload lacks it. Only Azure DevOps
-	// acts on this today (extra API call); it is a no-op for the other providers.
-	includeRemoteInfo?: boolean;
-	// Field selection for the row shape. GitHub-shaped because it is the only provider whose PR read gates
-	// anything on it; the others ignore it. Declared here rather than passed through a spread so a typo or a
-	// wrong-shaped map is a compile error instead of a silently ignored key. An ABSENT map means "select
-	// everything", so only summary reads pass one.
-	fields?: GitHubPullRequestFieldMap;
-}
-
-export interface GetPullRequestsForUserOptions {
-	includeFromArchivedRepos?: boolean;
-	cursor?: string; // stringified JSON object of type { type: 'cursor' | 'page'; value: string | number } | {}
-	baseUrl?: string;
-	// PR states to include; when omitted the provider returns its default (open only).
-	states?: GitPullRequestState[];
-	/**
-	 * Items to request per page. Worth setting explicitly on an account-wide read that gets DRAINED: each
-	 * provider falls back to its own historical page size when this is omitted, and GitHub's is 15
-	 * (`MAX_PR_PAGE_SIZE`), so a drain pays ~7x the round trips of the 100 its search actually allows.
-	 */
-	pageSize?: number;
-}
-
-export interface GetPullRequestsForUserInput extends GetPullRequestsForUserOptions {
-	userId: string;
-}
-
-export interface GetPullRequestsAssociatedWithUserInput extends GetPullRequestsForUserOptions {
-	username: string;
-}
-
-export interface GetPullRequestsForRepoInput extends GetPullRequestsOptions {
-	repo: GetRepoInput;
-}
-
-export interface GetPullRequestsForReposInput extends GetPullRequestsOptions {
-	repos: GetRepoInput[];
-}
-
-export interface GetPullRequestsForRepoIdsInput extends GetPullRequestsOptions {
-	repoIds: (string | number)[];
-}
-
-export interface GetIssuesOptions {
-	authorLogin?: string;
-	assigneeLogins?: string[];
-	mentionLogin?: string;
-	// Issue states to include; when omitted the provider returns its default (open only).
-	states?: GitIssueState[];
-	cursor?: string; // stringified JSON object of type { type: 'cursor' | 'page'; value: string | number } | {}
-	baseUrl?: string;
-	// 1-based page to request from numbered-page providers; takes precedence over a page-typed cursor.
-	page?: number;
-	// Items to request per page (numbered-page providers, plus GitHub's maxPageSize).
-	pageSize?: number;
-	/**
-	 * How the provider should order the result, as `field:direction`.
-	 *
-	 * Passed through to the SDK verbatim — the translation to each provider's own vocabulary lives THERE, next to
-	 * the capability map it validates against, so that the table this facade publishes and the table that does the
-	 * translating can't drift apart across two repositories. A key the provider can't express raises the SDK's
-	 * `UnsupportedSortError`, which is why the facade validates against `supportedIssueSorts` first: reaching that
-	 * error means this table has outrun the SDK's.
-	 *
-	 * Always supplied by the facade's reads, never omitted. Omitting it would delegate the order to each provider's
-	 * own default, which is the incoherence across providers the SDK deliberately preserves and this layer
-	 * deliberately does not.
-	 */
-	sort?: IssueSorting;
-}
-
-export interface GetIssuesForRepoInput extends GetIssuesOptions {
-	repo: GetRepoInput;
-}
-
-export interface GetIssuesForReposInput extends GetIssuesOptions {
-	repos: GetRepoInput[];
-}
-
-export interface GetIssuesForRepoIdsInput extends GetIssuesOptions {
-	repoIds: (string | number)[];
-}
-
-export interface GetIssuesForProjectInput extends GetIssuesOptions {
-	project: string;
-	resourceId: string;
-}
-
-export interface GetIssuesForAzureProjectInput extends GetIssuesOptions {
-	namespace: string;
-	project: string;
-}
-
-export interface GetReposOptions {
-	cursor?: string; // stringified JSON object of type { type: 'cursor' | 'page'; value: string | number } | {}
-}
-
-export interface GetReposForAzureProjectInput {
-	namespace: string;
-	project: string;
-}
-
-export interface PageInfo {
-	hasNextPage: boolean;
-	endCursor?: string | null;
-	nextPage?: number | null;
-	// Numbered-page providers (Bitbucket, Bitbucket Server, Azure DevOps) additionally report these.
-	currentPage?: number | null;
-	totalPages?: number | null;
-	totalCount?: number | null;
-}
-
-export type GetRepoFn = (
-	input: ProviderRepoInput,
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderRepository }>;
-export type GetRepoOfProjectFn = (
-	input: ProviderRepoInput & { project: string },
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderRepository }>;
-
-export type GetPullRequestsForReposFn = (
-	input: (GetPullRequestsForReposInput | GetPullRequestsForRepoIdsInput) & PagingInput,
-	options?: EnterpriseOptions,
-	// `metadata` carries SDK collection completeness/failures for multi-repo fan-outs (Bitbucket, Azure DevOps,
-	// Bitbucket Server); `pageInfo` is present for the cursor-based aggregate (GitHub). Both are optional so
-	// each provider only sets what it actually reports.
-) => Promise<{ data: ProviderPullRequest[]; pageInfo?: PageInfo; metadata?: CollectionMetadata }>;
-
-export type GetPullRequestsForRepoFn = (
-	input: GetPullRequestsForRepoInput & PagingInput,
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderPullRequest[]; pageInfo?: PageInfo }>;
-
-export type GetPullRequestsForUserFn = (
-	input: GetPullRequestsForUserInput | GetPullRequestsAssociatedWithUserInput,
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderPullRequest[]; pageInfo?: PageInfo }>;
-
-export type GetPullRequestsForAzureProjectsFn = (
-	input: {
-		projects: { namespace: string; project: string }[];
-		authorLogin?: string;
-		assigneeLogins?: string[];
-		reviewerId?: string;
-		states?: GitPullRequestState[];
-		repo?: ProviderRepoInput;
-	},
-	options?: EnterpriseOptions,
-	// Aggregate multi-project fan-out: no `pageInfo` (call getPullRequestsForAzureProject for that), but SDK
-	// collection metadata reports per-project completeness/failures.
-) => Promise<{ data: ProviderPullRequest[]; metadata?: CollectionMetadata }>;
-
-/** Single Azure project PR read, paginated by number (unlike the aggregate {@link GetPullRequestsForAzureProjectsFn}). */
-export type GetPullRequestsForAzureProjectFn = (
-	input: {
-		namespace: string;
-		project: string;
-		authorLogin?: string;
-		assigneeLogins?: string[];
-		reviewerId?: string;
-		states?: GitPullRequestState[];
-		repo?: ProviderRepoInput;
-	} & PagingInput,
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderPullRequest[]; pageInfo: { hasNextPage: boolean; nextPage: number | null } }>;
-
-export type MergePullRequestFn =
-	| ((
-			input: {
-				pullRequest: {
-					headRef: {
-						oid: string | null;
-					} | null;
-					version?: number; // Used by BitbucketServer
-				} & SetPullRequestInput;
-				mergeStrategy?: GitMergeStrategy;
-			},
-			options?: EnterpriseOptions,
-	  ) => Promise<void>)
-	| ((
-			input: {
-				pullRequest: {
-					headRef: {
-						oid: string | null;
-					} | null;
-				} & SetPullRequestInput;
-				mergeStrategy?: GitMergeStrategy.Squash;
-			},
-			options?: EnterpriseOptions,
-	  ) => Promise<void>)
-	| ((
-			input: {
-				pullRequest: {
-					headRef: {
-						oid: string;
-					};
-				} & AzureSetPullRequestInput;
-				mergeStrategy?:
-					| GitMergeStrategy.MergeCommit
-					| GitMergeStrategy.Rebase
-					| GitMergeStrategy.RebaseThenMergeCommit
-					| GitMergeStrategy.Squash;
-			},
-			options?: EnterpriseOptions,
-	  ) => Promise<void>);
-
-export type GetIssueFn = (
-	input:
-		| { resourceId: string; number: string } // jira
-		| { namespace: string; name: string; number: string }, // gitlab
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderIssue }>;
-
-export type GetIssuesForReposFn = (
-	input: (GetIssuesForReposInput | GetIssuesForRepoIdsInput) & PagingInput,
-	options?: EnterpriseOptions,
-	// GitHub's multi-repo issue search reports its 1,000-result cap — and, when it recovers past it by
-	// partitioning, what that recovery could not reach — through `metadata`. Documented on the contract for
-	// the reader; `getPagedResult` accepts and forwards `metadata` from any provider fn regardless.
-) => Promise<{ data: ProviderIssue[]; pageInfo?: PageInfo; metadata?: CollectionMetadata }>;
-
-export type GetIssuesForCurrentUserInput = PagingInput & {
-	// GitLab's account-wide REST read (`GET /issues`): `scope` controls breadth ('assigned_to_me' vs 'all') and
-	// the username fields independently narrow a broad read to a specific assignee or author. Other providers
-	// (Linear) ignore these and page purely off the cursor.
-	scope?: 'assigned_to_me' | 'all';
-	assigneeUsername?: string;
-	authorUsername?: string;
-	pageSize?: number;
-	/** See {@link GetIssuesOptions.sort}. */
-	sort?: IssueSorting;
-};
-
-export type GetIssuesForCurrentUserFn = (
-	input: GetIssuesForCurrentUserInput,
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderIssue[]; pageInfo?: PageInfo }>;
-
-export type GetIssuesForRepoFn = (
-	input: GetIssuesForRepoInput & PagingInput,
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderIssue[]; pageInfo?: PageInfo }>;
-
-export type GetIssuesForAzureProjectFn = (
-	input: GetIssuesForAzureProjectInput & PagingInput,
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderIssue[]; pageInfo?: PageInfo }>;
-
-export type GetReposForAzureProjectFn = (
-	input: GetReposForAzureProjectInput & PagingInput,
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderRepository[]; pageInfo?: PageInfo }>;
-
-export type GetOrgsForCurrentUserFn = (
-	input?: CursorPageInput,
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderGitHubOrganization[]; pageInfo?: PageInfo }>;
-export type GetReposForOrgFn = (
-	input: { orgName: string } & PagingInput,
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderRepository[]; pageInfo?: PageInfo }>;
-export type GetReposForWorkspaceFn = (
-	input: { workspace: string } & PagingInput,
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderRepository[]; pageInfo?: PageInfo }>;
-export type GetReposForCurrentUserFn = (
-	// `affiliations` narrows GitHub's `/user/repos` read (owner/collaborator/organization_member);
-	// GitLab's equivalent read ignores it.
-	input: PagingInput & { affiliations?: ('owner' | 'collaborator' | 'organization_member')[] },
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderRepository[]; pageInfo?: PageInfo }>;
-export type GetGroupsForCurrentUserFn = (
-	input?: { topLevelOnly?: boolean } & PagingInput,
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderGitLabGroup[]; pageInfo?: PageInfo }>;
-
-export type GetCurrentUserFn = (
-	input: Record<string, never>,
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderAccount }>;
-export type GetCurrentUserForInstanceFn = (
-	input: { namespace: string },
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderAccount }>;
-export type GetCurrentUserForResourceFn = (
-	input: { resourceId: string },
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderAccount }>;
-
-export type GetJiraResourcesForCurrentUserFn = (options?: EnterpriseOptions) => Promise<{ data: JiraResource[] }>;
-export type GetLinearOrganizationFn = (options?: EnterpriseOptions) => Promise<{ data: LinearOrganization }>;
-export type GetLinearTeamsForCurrentUserFn = (options?: EnterpriseOptions) => Promise<{ data: LinearTeam[] }>;
-export type GetLinearIssuesFn = (
-	input: { teams?: string[]; projects?: string[]; labels?: string[] } & PagingInput,
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderIssue[]; pageInfo?: PageInfo }>;
-/**
- * Linear's current-user (viewer) query. Its raw `@linear/sdk` User isn't a `ProviderAccount` (no
- * username/avatar/url), so it's typed with the minimal fields the viewer query actually returns rather than
- * importing `@linear/sdk` (which is bundled in the SDK dist and not a resolvable top-level dependency).
- */
-export type GetLinearCurrentUserFn = (
-	options?: EnterpriseOptions,
-) => Promise<{ data: { id: string; name?: string | null; email?: string | null; displayName?: string | null } }>;
-export type GetJiraProjectsForResourcesFn = (
-	input: { resourceIds: string[] },
-	options?: EnterpriseOptions,
-	// Fan-out across resources: preserves successful resources' projects and reports per-resource failures in
-	// SDK collection metadata instead of throwing when a single resource fails.
-) => Promise<{ data: JiraProject[]; metadata?: CollectionMetadata }>;
-export type GetJiraProjectsForResourceFn = (
-	input: { resourceId: string } & CursorPageInput,
-	options?: EnterpriseOptions,
-) => Promise<{ data: JiraProject[]; pageInfo?: PageInfo; metadata?: CollectionMetadata }>;
-export type GetGitLabPullRequestsForUserAssociationFn = (
-	input: {
-		username: string;
-		association: 'assigned' | 'authored' | 'reviewRequested';
-		includeFromArchivedRepos?: boolean;
-		labelNames?: string[];
-		repo?: ProviderRepoInput;
-		states?: GitPullRequestState[];
-		pageSize?: number;
-	} & CursorPageInput,
-	options?: EnterpriseOptions,
-) => Promise<{ data: ProviderPullRequest[]; pageInfo?: PageInfo }>;
-export type GetAzureResourcesForUserFn = (
-	input: { userId: string },
-	options?: EnterpriseOptions,
-) => Promise<{ data: AzureOrganization[] }>;
-export type GetAzureProjectsForResourceFn = (
-	input: { namespace: string; cursor?: string },
-	options?: EnterpriseOptions,
-) => Promise<{ data: AzureProject[]; pageInfo?: PageInfo }>;
-export type GetBitbucketResourcesForCurrentUserFn = (
-	input: { page?: number },
-	options?: EnterpriseOptions,
-) => Promise<{ data: BitbucketWorkspaceStub[]; pageInfo?: PageInfo }>;
-export type GetBitbucketPullRequestsAuthoredByUserForWorkspaceFn = (
-	input: {
-		userId: string;
-		workspaceSlug: string;
-		states?: GitPullRequestState[];
-	} & NumberedPageInput,
-	options?: EnterpriseOptions,
-) => Promise<{
-	pageInfo: {
-		hasNextPage: boolean;
-		nextPage: number | null;
-	};
-	data: GitPullRequest[];
-}>;
-export type GetBitbucketServerPullRequestsForCurrentUserFn = (
-	input: { states?: GitPullRequestState[] } & NumberedPageInput,
-	options?: EnterpriseOptions,
-) => Promise<{
-	pageInfo: {
-		hasNextPage: boolean;
-		nextPage: number | null;
-	};
-	data: GitPullRequest[];
-}>;
-export type GetIssuesForProjectFn = Jira['getIssuesForProject'];
-// Derived from the client method rather than hand-declared, as its project-scoped sibling above already is: the
-// hand-written shape named only `resourceId`, so every other field the SDK accepts (the cursor, the sort, the
-// transitions switch) was invisible to the type system and had to be smuggled through `getPagedResult`'s `any`.
-export type GetIssuesForResourceForCurrentUserFn = Jira['getIssuesForResourceForCurrentUser'];
-
-// Trello reads (issues-capable provider). The Trello client is keyed by an `appKey` (the Trello app key from
-// the cloud token exchange) alongside the OAuth token, so these mirror the client method shapes directly.
-export type GetTrelloCurrentUserFn = Trello['getCurrentUser'];
-export type GetTrelloBoardsForCurrentUserFn = Trello['getBoardsForCurrentUser'];
-export type GetTrelloListsForBoardFn = Trello['getListsForTrelloBoard'];
-export type GetTrelloAccountForIdFn = Trello['getAccountForId'];
-export type GetTrelloIssuesForBoardFn = Trello['getIssuesForBoard'];
-export type GetTrelloLabelsForBoardFn = Trello['getLabelsForBoard'];
-
-export interface ProviderInfo extends ProviderMetadata {
-	provider: GitHub | GitLab | Bitbucket | BitbucketServer | Jira | Linear | Trello | AzureDevOps;
-	getRepoFn?: GetRepoFn;
-	getRepoOfProjectFn?: GetRepoOfProjectFn;
-	getPullRequestsForReposFn?: GetPullRequestsForReposFn;
-	getPullRequestsForRepoFn?: GetPullRequestsForRepoFn;
-	getPullRequestsForUserFn?: GetPullRequestsForUserFn;
-	getGitLabPullRequestsForUserAssociationFn?: GetGitLabPullRequestsForUserAssociationFn;
-	getPullRequestsForAzureProjectsFn?: GetPullRequestsForAzureProjectsFn;
-	getPullRequestsForAzureProjectFn?: GetPullRequestsForAzureProjectFn;
-	getIssueFn?: GetIssueFn;
-	getIssuesForReposFn?: GetIssuesForReposFn;
-	getIssuesForCurrentUserFn?: GetIssuesForCurrentUserFn;
-	getIssuesForRepoFn?: GetIssuesForRepoFn;
-	getIssuesForAzureProjectFn?: GetIssuesForAzureProjectFn;
-	getCurrentUserFn?: GetCurrentUserFn;
-	getCurrentUserForInstanceFn?: GetCurrentUserForInstanceFn;
-	getCurrentUserForResourceFn?: GetCurrentUserForResourceFn;
-	getJiraResourcesForCurrentUserFn?: GetJiraResourcesForCurrentUserFn;
-	getLinearOrganizationFn?: GetLinearOrganizationFn;
-	getLinearTeamsForCurrentUserFn?: GetLinearTeamsForCurrentUserFn;
-	getLinearIssuesFn?: GetLinearIssuesFn;
-	getLinearCurrentUserFn?: GetLinearCurrentUserFn;
-	getAzureResourcesForUserFn?: GetAzureResourcesForUserFn;
-	getBitbucketResourcesForCurrentUserFn?: GetBitbucketResourcesForCurrentUserFn;
-	getBitbucketPullRequestsAuthoredByUserForWorkspaceFn?: GetBitbucketPullRequestsAuthoredByUserForWorkspaceFn;
-	getBitbucketServerPullRequestsForCurrentUserFn?: GetBitbucketServerPullRequestsForCurrentUserFn;
-	getJiraProjectsForResourcesFn?: GetJiraProjectsForResourcesFn;
-	getJiraProjectsForResourceFn?: GetJiraProjectsForResourceFn;
-	getAzureProjectsForResourceFn?: GetAzureProjectsForResourceFn;
-	getIssuesForProjectFn?: GetIssuesForProjectFn;
-	getReposForAzureProjectFn?: GetReposForAzureProjectFn;
-	getIssuesForResourceForCurrentUserFn?: GetIssuesForResourceForCurrentUserFn;
-	mergePullRequestFn?: MergePullRequestFn;
-	getOrgsForCurrentUserFn?: GetOrgsForCurrentUserFn;
-	getReposForOrgFn?: GetReposForOrgFn;
-	getReposForWorkspaceFn?: GetReposForWorkspaceFn;
-	getReposForCurrentUserFn?: GetReposForCurrentUserFn;
-	getGroupsForCurrentUserFn?: GetGroupsForCurrentUserFn;
-	getTrelloCurrentUserFn?: GetTrelloCurrentUserFn;
-	getTrelloBoardsForCurrentUserFn?: GetTrelloBoardsForCurrentUserFn;
-	getTrelloListsForBoardFn?: GetTrelloListsForBoardFn;
-	getTrelloAccountForIdFn?: GetTrelloAccountForIdFn;
-	getTrelloIssuesForBoardFn?: GetTrelloIssuesForBoardFn;
-	getTrelloLabelsForBoardFn?: GetTrelloLabelsForBoardFn;
-}
-
-export interface ProviderMetadata {
-	domain: string;
-	id: IntegrationIds;
-	name: string;
-	type: IntegrationType;
-	/** Key for the `gl-provider-<iconKey>` glicon. Cloud self-managed variants reuse the base
-	 * `'github-enterprise'`/`'gitlab-self-hosted'` icon (no enum member exists for those anymore). */
-	iconKey: string;
-	issuesPagingMode?: PagingMode;
-	pullRequestsPagingMode?: PagingMode;
-	scopes: string[];
-	supportedPullRequestFilters?: PullRequestFilter[];
-	/**
-	 * Relationship filters the ACCOUNT-WIDE pull-request read can express as an exact OR union.
-	 * This is independent from `supportedPullRequestFilters`, which describes repo-scoped reads.
-	 */
-	supportedAccountWidePullRequestFilters?: PullRequestFilter[];
-	/**
-	 * What the filtered pull-request search can express server-side. Absent means the provider has
-	 * no such search and the facade refuses it rather than returning an unfiltered page.
-	 */
-	supportedPullRequestSearch?: PullRequestSearchCapabilities;
-	/**
-	 * Maximum results the provider will serve for one pull-request search facet. Matches beyond it are unreachable
-	 * and are reported as a succeeded omission carrying this limit plus the provider's pre-ceiling facet count.
-	 */
-	pullRequestSearchResultLimit?: number;
-	/** Filters the REPO-scoped issue read can express. */
-	supportedIssueFilters?: IssueFilter[];
-	/**
-	 * Filters the ACCOUNT-WIDE issue read can express, which is NOT the same set as
-	 * {@link ProviderMetadata.supportedIssueFilters}: the two reads are different provider queries.
-	 *
-	 * Unfiltered, each provider's account-wide read is that provider's own definition of "my issues" — GitHub/GHE
-	 * union authored + assigned + mentioned, Azure drains assigned + authored, and GitLab reads assigned-to-me.
-	 * A consumer replacing a narrower tool (`gk`'s `assignee:@me`) must select the `Assignee` filter wherever the
-	 * provider's default is wider.
-	 *
-	 * A filter listed here narrows that read server-side. Absent/empty means the read can't be narrowed at all,
-	 * so the facade refuses a filtered request rather than serving the unnarrowed union as if it had been
-	 * filtered. GitLab lists `Assignee` and `Author` because the SDK's account-wide input exposes both username
-	 * axes; it omits `Mention` because that REST read has no first-class mention filter.
-	 */
-	supportedAccountWideIssueFilters?: IssueFilter[];
-	/**
-	 * Sort keys the REPO-scoped issue read can express server-side — and, for an issue tracker (Jira/Linear/Trello),
-	 * its project-scoped read, which is the only issue surface a tracker has.
-	 *
-	 * Absent/empty means the read can't be ordered at all, so a request carrying `sort` is refused rather than
-	 * served in whatever order the provider felt like. Present, it is a promise: every key here reaches the
-	 * provider query.
-	 *
-	 * A key listed here is expressible on ONE provider query, which is what this read is when it is given ONE
-	 * scope. Given several (GitLab across repositories, Azure across projects, a tracker across projects) it merges
-	 * their results here and can only honor a key a normalized issue carries, so it additionally refuses
-	 * `priority`/`dueDate`/`resolved` — see `getIssueComparator`. That depends on the caller's scope count rather
-	 * than on the provider, which is why it is a runtime refusal and not a fourth table: encoding it here would
-	 * under-report the single-scope read, which really does support those keys.
-	 */
-	supportedIssueSorts?: IssueSorting[];
-	/**
-	 * Sort keys the ACCOUNT-WIDE issue read can express server-side, which is NOT the same set as
-	 * {@link ProviderMetadata.supportedIssueSorts} — for GitLab the two reads are different APIs (GraphQL vs REST)
-	 * with genuinely different vocabularies, not one narrowed twice.
-	 *
-	 * Absent means the account-wide read can't be ordered (or doesn't exist). An issue tracker leaves this empty
-	 * and reports under `supportedIssueSorts`, so reading a tracker's capability from here under-reports it.
-	 *
-	 * Unlike {@link ProviderMetadata.supportedIssueSorts} this needs no companion runtime refusal, because every
-	 * provider's account-wide read is a union of several queries with no scope count for a caller to reduce: it
-	 * ALWAYS merges. So the keys a merge can't order by are simply absent here — the table states what the read can
-	 * honor, which is what makes intersecting against it sufficient.
-	 */
-	supportedAccountWideIssueSorts?: IssueSorting[];
-	/**
-	 * What the provider's FILTERED issue search (`searchIssuesPage`, and the `countIssues` probe over the same
-	 * criteria) can express server-side. A third, wider surface than either filter set above: it is not bound to
-	 * the user at all, so it takes relationships those reads have no way to name (`any-assignee`, `unassigned`),
-	 * plus free text and issue attributes.
-	 *
-	 * Absent means the provider has NO filtered issue search and the read is refused. Present, it is a promise:
-	 * every field declared here reaches the provider query, so a consumer that intersects against it never has a
-	 * read refused, and a criterion is never silently ignored.
-	 */
-	supportedIssueSearch?: IssueSearchCapabilities;
-	/**
-	 * The maximum number of results the provider's filtered issue search will serve for ONE query, however it is
-	 * paged. Matches past it are UNREACHABLE, not merely unfetched, which is why a read that hits this reports an
-	 * omission with `recovery: 'none'` and the total match count rather than offering a "load more".
-	 *
-	 * Absent means the provider declares no ceiling, in which case a truncated read falls back to generic wording
-	 * instead of quoting a limit that was never published.
-	 */
-	issueSearchResultLimit?: number;
-}
-
-export type Providers = Record<IntegrationIds, ProviderInfo>;
-export type ProvidersMetadata = Record<IntegrationIds, ProviderMetadata>;
-
-/**
- * GitHub and GitHub Enterprise express every criterion as a search qualifier on the same GraphQL `search` field,
- * so the two share one declaration — a GHE instance running the same search syntax has the same capability, and
- * two copies of this table would be free to drift.
- *
- * Every entry is a claim the implementation must keep: `searchIssuesPage` emits a qualifier for each of these,
- * and a test asserts that (see the `issueSearch` capability tests) so the table can't quietly outrun the code.
- */
-const githubIssueSearchCapabilities: IssueSearchCapabilities = {
-	// `author:@me` / `assignee:@me` / `mentions:@me` / `assignee:*` / `no:assignee`, each its own aliased search.
-	relationships: ['authored', 'assigned', 'mentioned', 'any-assignee', 'unassigned'],
-	text: true,
-	labels: true,
-	milestone: true,
-	updatedAfter: true,
-	createdAfter: true,
-	// `-linked:pr`.
-	withoutLinkedPullRequest: true,
-	// `is:open` / `is:closed`, or neither for all states.
-	states: true,
-	// `sort:created-desc`, `sort:updated`, `sort:comments-asc`, … — see `githubIssueSorts`.
-	sorts: githubIssueSorts,
-};
-
-/**
- * The ordering vocabulary of GitHub's filtered PR search: `created` and `updated`, both directions.
- *
- * Hand-declared rather than derived from `@gitkraken/provider-apis` (which has no PR-sort surface), and narrower
- * than the issue set on purpose: the merged relationship × state facets can only be re-ordered by a field a
- * `PullRequestShape` carries (see `getPullRequestComparator`), and GitHub PRs have no priority and no relevance
- * that orders stably under the result ceiling. A parity test pins this to `gitHubPullRequestSortQualifiers`' keys
- * so the capability can't outrun the emitter.
- */
-const githubPullRequestSorts: PullRequestSorting[] = ['updated:desc', 'updated:asc', 'created:desc', 'created:asc'];
-
-/** GitHub and GHE use the same filtered pull-request search syntax and result ceiling. */
-const githubPullRequestSearchCapabilities: PullRequestSearchCapabilities = {
-	relationships: [
-		PullRequestFilter.Author,
-		PullRequestFilter.Assignee,
-		PullRequestFilter.ReviewRequested,
-		PullRequestFilter.Reviewed,
-		PullRequestFilter.Mention,
-	],
-	states: ['open', 'closed', 'merged', 'all'],
-	text: true,
-	updatedAfter: true,
-	createdAfter: true,
-	includeArchived: true,
-	draft: true,
-	repositoryScope: true,
-	organizationScope: true,
-	// `sort:updated`, `sort:updated-asc`, `sort:created-desc`, `sort:created-asc` — see `githubPullRequestSorts`.
-	sorts: githubPullRequestSorts,
-};
-
-export const providersMetadata: ProvidersMetadata = {
-	[GitCloudHostIntegrationId.GitHub]: {
-		domain: 'github.com',
-		id: GitCloudHostIntegrationId.GitHub,
-		name: 'GitHub',
-		type: 'git',
-		iconKey: GitCloudHostIntegrationId.GitHub,
-		issuesPagingMode: PagingMode.Repos,
-		pullRequestsPagingMode: PagingMode.Repos,
-		// Use 'username' property on account for PR filters
-		supportedPullRequestFilters: [
-			PullRequestFilter.Author,
-			PullRequestFilter.Assignee,
-			PullRequestFilter.ReviewRequested,
-			PullRequestFilter.Mention,
-		],
-		supportedAccountWidePullRequestFilters: [
-			PullRequestFilter.Author,
-			PullRequestFilter.Assignee,
-			PullRequestFilter.ReviewRequested,
-			PullRequestFilter.Reviewed,
-			PullRequestFilter.Mention,
-		],
-		supportedPullRequestSearch: githubPullRequestSearchCapabilities,
-		pullRequestSearchResultLimit: githubSearchResultLimit,
-		// Use 'username' property on account for issue filters
-		supportedIssueFilters: [IssueFilter.Author, IssueFilter.Assignee, IssueFilter.Mention],
-		// The account-wide read is three independent searches (`author:@me`, `assignee:@me`, `mentions:@me`) behind
-		// one composite cursor, so any subset of them is expressible.
-		supportedAccountWideIssueFilters: [IssueFilter.Author, IssueFilter.Assignee, IssueFilter.Mention],
-		// One `search` field serves all three issue reads (repo-scoped, account-wide, filtered search), so the same
-		// qualifiers are expressible on each — the account-wide one narrowed to what its three-alias merge can order.
-		supportedIssueSorts: githubIssueSorts,
-		supportedAccountWideIssueSorts: githubAccountWideIssueSorts,
-		supportedIssueSearch: githubIssueSearchCapabilities,
-		issueSearchResultLimit: githubSearchResultLimit,
-		scopes: ['repo', 'read:user', 'user:email'],
-	},
-	[GitSelfManagedHostIntegrationId.CloudGitHubEnterprise]: {
-		domain: '',
-		id: GitSelfManagedHostIntegrationId.CloudGitHubEnterprise,
-		name: 'GitHub Enterprise',
-		type: 'git',
-		iconKey: 'github-enterprise',
-		issuesPagingMode: PagingMode.Repos,
-		pullRequestsPagingMode: PagingMode.Repos,
-		// Use 'username' property on account for PR filters
-		supportedPullRequestFilters: [
-			PullRequestFilter.Author,
-			PullRequestFilter.Assignee,
-			PullRequestFilter.ReviewRequested,
-			PullRequestFilter.Mention,
-		],
-		supportedAccountWidePullRequestFilters: [
-			PullRequestFilter.Author,
-			PullRequestFilter.Assignee,
-			PullRequestFilter.ReviewRequested,
-			PullRequestFilter.Reviewed,
-			PullRequestFilter.Mention,
-		],
-		supportedPullRequestSearch: githubPullRequestSearchCapabilities,
-		pullRequestSearchResultLimit: githubSearchResultLimit,
-		// Use 'username' property on account for issue filters
-		supportedIssueFilters: [IssueFilter.Author, IssueFilter.Assignee, IssueFilter.Mention],
-		// The account-wide read is three independent searches (`author:@me`, `assignee:@me`, `mentions:@me`) behind
-		// one composite cursor, so any subset of them is expressible.
-		supportedAccountWideIssueFilters: [IssueFilter.Author, IssueFilter.Assignee, IssueFilter.Mention],
-		// One `search` field serves all three issue reads (repo-scoped, account-wide, filtered search), so the same
-		// qualifiers are expressible on each — the account-wide one narrowed to what its three-alias merge can order.
-		supportedIssueSorts: githubIssueSorts,
-		supportedAccountWideIssueSorts: githubAccountWideIssueSorts,
-		supportedIssueSearch: githubIssueSearchCapabilities,
-		issueSearchResultLimit: githubSearchResultLimit,
-		scopes: ['repo', 'read:user', 'user:email'],
-	},
-	[GitCloudHostIntegrationId.GitLab]: {
-		domain: 'gitlab.com',
-		id: GitCloudHostIntegrationId.GitLab,
-		name: 'GitLab',
-		type: 'git',
-		iconKey: GitCloudHostIntegrationId.GitLab,
-		issuesPagingMode: PagingMode.Repo,
-		pullRequestsPagingMode: PagingMode.Repo,
-		// Use 'username' property on account for PR filters
-		supportedPullRequestFilters: [
-			PullRequestFilter.Author,
-			PullRequestFilter.Assignee,
-			PullRequestFilter.ReviewRequested,
-		],
-		supportedAccountWidePullRequestFilters: [
-			PullRequestFilter.Author,
-			PullRequestFilter.Assignee,
-			PullRequestFilter.ReviewRequested,
-		],
-		// Use 'username' property on account for issue filters
-		supportedIssueFilters: [IssueFilter.Author, IssueFilter.Assignee],
-		// The account-wide read drains one `scope=assigned_to_me` pass and one `scope=all` + `authorUsername` pass,
-		// unioned, so either axis is expressible on its own. Mention is absent because GitLab's REST issue read has
-		// no first-class mention filter to narrow with.
-		supportedAccountWideIssueFilters: [IssueFilter.Assignee, IssueFilter.Author],
-		// Two different surfaces, not one narrowed twice: the repository-scoped read is GraphQL and the
-		// account-wide one is REST, and REST has neither `title` nor `closed_at`.
-		supportedIssueSorts: gitlabIssueSorts,
-		supportedAccountWideIssueSorts: gitlabAccountWideIssueSorts,
-		scopes: ['api', 'read_user', 'read_repository'],
-	},
-	[GitSelfManagedHostIntegrationId.CloudGitLabSelfHosted]: {
-		domain: '',
-		id: GitSelfManagedHostIntegrationId.CloudGitLabSelfHosted,
-		name: 'GitLab Self-Hosted',
-		type: 'git',
-		iconKey: 'gitlab-self-hosted',
-		issuesPagingMode: PagingMode.Repo,
-		pullRequestsPagingMode: PagingMode.Repo,
-		// Use 'username' property on account for PR filters
-		supportedPullRequestFilters: [
-			PullRequestFilter.Author,
-			PullRequestFilter.Assignee,
-			PullRequestFilter.ReviewRequested,
-		],
-		supportedAccountWidePullRequestFilters: [
-			PullRequestFilter.Author,
-			PullRequestFilter.Assignee,
-			PullRequestFilter.ReviewRequested,
-		],
-		// Use 'username' property on account for issue filters
-		supportedIssueFilters: [IssueFilter.Author, IssueFilter.Assignee],
-		// The account-wide read drains one `scope=assigned_to_me` pass and one `scope=all` + `authorUsername` pass,
-		// unioned, so either axis is expressible on its own. Mention is absent because GitLab's REST issue read has
-		// no first-class mention filter to narrow with.
-		supportedAccountWideIssueFilters: [IssueFilter.Assignee, IssueFilter.Author],
-		// Two different surfaces, not one narrowed twice: the repository-scoped read is GraphQL and the
-		// account-wide one is REST, and REST has neither `title` nor `closed_at`.
-		supportedIssueSorts: gitlabIssueSorts,
-		supportedAccountWideIssueSorts: gitlabAccountWideIssueSorts,
-		scopes: ['api', 'read_user', 'read_repository'],
-	},
-	[GitCloudHostIntegrationId.Bitbucket]: {
-		domain: 'bitbucket.org',
-		id: GitCloudHostIntegrationId.Bitbucket,
-		name: 'Bitbucket',
-		type: 'git',
-		iconKey: GitCloudHostIntegrationId.Bitbucket,
-		pullRequestsPagingMode: PagingMode.Repo,
-		// Use 'id' property on account for PR filters (reviewer filter keyed by account id / reviewerId)
-		supportedPullRequestFilters: [PullRequestFilter.Author, PullRequestFilter.ReviewRequested],
-		supportedAccountWidePullRequestFilters: [PullRequestFilter.Author, PullRequestFilter.ReviewRequested],
-		scopes: ['account:read', 'repository:read', 'pullrequest:read', 'issue:read'],
-	},
-	[GitSelfManagedHostIntegrationId.BitbucketServer]: {
-		domain: '',
-		id: GitSelfManagedHostIntegrationId.BitbucketServer,
-		name: 'Bitbucket Data Center',
-		type: 'git',
-		iconKey: GitSelfManagedHostIntegrationId.BitbucketServer,
-		supportedPullRequestFilters: [PullRequestFilter.Author, PullRequestFilter.ReviewRequested],
-		supportedAccountWidePullRequestFilters: [PullRequestFilter.Author, PullRequestFilter.ReviewRequested],
-		scopes: ['Project (Read)', 'Repository (Write)'],
-	},
-	[GitCloudHostIntegrationId.AzureDevOps]: {
-		domain: 'dev.azure.com',
-		id: GitCloudHostIntegrationId.AzureDevOps,
-		name: 'Azure DevOps',
-		type: 'git',
-		iconKey: GitCloudHostIntegrationId.AzureDevOps,
-		issuesPagingMode: PagingMode.Project,
-		pullRequestsPagingMode: PagingMode.Repo,
-		// Use 'id' property on account for PR filters (reviewer filter keyed by account id / reviewerId)
-		supportedPullRequestFilters: [
-			PullRequestFilter.Author,
-			PullRequestFilter.Assignee,
-			PullRequestFilter.ReviewRequested,
-		],
-		supportedAccountWidePullRequestFilters: [
-			PullRequestFilter.Author,
-			PullRequestFilter.Assignee,
-			PullRequestFilter.ReviewRequested,
-		],
-		// Use 'name' property on account for issue filters
-		supportedIssueFilters: [IssueFilter.Author, IssueFilter.Assignee, IssueFilter.Mention],
-		// The account-wide read drains one (project × assignee) and one (project × author) query per project, so
-		// either axis is expressible on its own. There is no mention query to narrow to.
-		supportedAccountWideIssueFilters: [IssueFilter.Author, IssueFilter.Assignee],
-		// Both reads emit the same WIQL, but the account-wide one drains every (project x relationship) query and
-		// merges the results, so it can only honor keys a normalized issue carries — `resolved` and `priority` are
-		// dropped from that surface for the same reason they are dropped from GitLab's.
-		supportedIssueSorts: azureIssueSorts,
-		supportedAccountWideIssueSorts: azureAccountWideIssueSorts,
-		scopes: ['vso.code', 'vso.identity', 'vso.project', 'vso.profile', 'vso.work'],
-	},
-	[GitSelfManagedHostIntegrationId.AzureDevOpsServer]: {
-		domain: '',
-		id: GitSelfManagedHostIntegrationId.AzureDevOpsServer,
-		name: 'Azure DevOps Server',
-		type: 'git',
-		iconKey: GitCloudHostIntegrationId.AzureDevOps,
-		issuesPagingMode: PagingMode.Project,
-		pullRequestsPagingMode: PagingMode.Repo,
-		// Use 'id' property on account for PR filters (reviewer filter keyed by account id / reviewerId)
-		supportedPullRequestFilters: [
-			PullRequestFilter.Author,
-			PullRequestFilter.Assignee,
-			PullRequestFilter.ReviewRequested,
-		],
-		supportedAccountWidePullRequestFilters: [
-			PullRequestFilter.Author,
-			PullRequestFilter.Assignee,
-			PullRequestFilter.ReviewRequested,
-		],
-		// Use 'name' property on account for issue filters
-		supportedIssueFilters: [IssueFilter.Author, IssueFilter.Assignee, IssueFilter.Mention],
-		// The account-wide read drains one (project × assignee) and one (project × author) query per project, so
-		// either axis is expressible on its own. There is no mention query to narrow to.
-		supportedAccountWideIssueFilters: [IssueFilter.Author, IssueFilter.Assignee],
-		// Both reads emit the same WIQL, but the account-wide one drains every (project x relationship) query and
-		// merges the results, so it can only honor keys a normalized issue carries — `resolved` and `priority` are
-		// dropped from that surface for the same reason they are dropped from GitLab's.
-		supportedIssueSorts: azureIssueSorts,
-		supportedAccountWideIssueSorts: azureAccountWideIssueSorts,
-		scopes: ['vso.code', 'vso.identity', 'vso.project', 'vso.profile', 'vso.work'],
-	},
-	[IssuesCloudHostIntegrationId.Jira]: {
-		domain: 'atlassian.net',
-		id: IssuesCloudHostIntegrationId.Jira,
-		name: 'Jira',
-		type: 'issues',
-		iconKey: IssuesCloudHostIntegrationId.Jira,
-		scopes: [
-			'read:status:jira',
-			'read:application-role:jira',
-			'write:attachment:jira',
-			'read:comment:jira',
-			'read:project-category:jira',
-			'read:project:jira',
-			'read:issue.vote:jira',
-			'read:field-configuration:jira',
-			'write:issue:jira',
-			'read:issue-security-level:jira',
-			'write:issue.property:jira',
-			'read:issue.changelog:jira',
-			'read:avatar:jira',
-			'read:issue-meta:jira',
-			'read:permission:jira',
-			'offline_access',
-			'read:issue:jira',
-			'read:me',
-			'read:audit-log:jira',
-			'read:project.component:jira',
-			'read:group:jira',
-			'read:project-role:jira',
-			'write:comment:jira',
-			'read:label:jira',
-			'write:comment.property:jira',
-			'read:issue-details:jira',
-			'read:issue-type-hierarchy:jira',
-			'read:issue.transition:jira',
-			'read:user:jira',
-			'read:field:jira',
-			'read:issue-type:jira',
-			'read:project.property:jira',
-			'read:comment.property:jira',
-			'read:project-version:jira',
-		],
-		supportedIssueFilters: [IssueFilter.Author, IssueFilter.Assignee, IssueFilter.Mention],
-		// A tracker's issues live under resource -> project, so it has no account-wide surface to declare: its
-		// capability is reported under `issues`, which is what `listIssueTrackerIssuesPage` validates against.
-		supportedIssueSorts: jiraIssueSorts,
-	},
-	[IssuesCloudHostIntegrationId.Linear]: {
-		domain: 'linear.app',
-		id: IssuesCloudHostIntegrationId.Linear,
-		name: 'Linear',
-		type: 'issues',
-		iconKey: IssuesCloudHostIntegrationId.Linear,
-		scopes: [],
-		// Linear scopes "my issues" client-side by the viewer's assignee id; author/mention aren't supported.
-		supportedIssueFilters: [IssueFilter.Assignee],
-		// Both directions, and one table for both reads: they are the same root `issues` query taking the same
-		// `sort` argument, so there is no account-wide narrowing to declare.
-		supportedIssueSorts: linearIssueSorts,
-	},
-	[IssuesCloudHostIntegrationId.Trello]: {
-		domain: 'trello.com',
-		id: IssuesCloudHostIntegrationId.Trello,
-		name: 'Trello',
-		type: 'issues',
-		iconKey: IssuesCloudHostIntegrationId.Trello,
-		scopes: [],
-		// Trello cards are filtered by the assignee (member) only; author/mention have no Trello equivalent.
-		supportedIssueFilters: [IssueFilter.Assignee],
-		// `sort:edited` / `sort:-edited`. Trello's other search sorts (`created`, `due`) have no card-order effect.
-		supportedIssueSorts: trelloIssueSorts,
-	},
-};
-
-export function getReasonsForUserIssue(issue: ProviderIssue, userLogin: string): string[] {
-	const reasons: string[] = [];
-	let isAuthor = false;
-	let isAssignee = false;
-	if (issue.author?.username === userLogin || issue.author?.name === userLogin) {
-		reasons.push('authored');
-		isAuthor = true;
-	}
-	if (issue.assignees?.some(assignee => assignee.username === userLogin || assignee.name === userLogin)) {
-		reasons.push('assigned');
-		isAssignee = true;
-	}
-
-	// TODO: Impossible to denote all issues we are mentioned on given their properties. for now just
-	// assume we are mentioned on any of our issues we are not the author or assignee on
-	if (!isAuthor && !isAssignee) {
-		reasons.push('mentioned');
-	}
-
-	return reasons;
-}
-
-function toIssueIdentifier(value: string | number): string {
-	return String(value);
-}
-
-export function toIssueShape(
-	issue: ProviderIssue,
-	provider: ProviderReference,
-	options?: { reliableStateCategory?: boolean },
-): IssueShape | undefined {
-	// TODO: Add some protections/baselines rather than killing the transformation here
-	// `author` is intentionally not required: some providers have no per-item creator (e.g. Trello cards,
-	// which the SDK maps with `author: null`), and dropping every such item would discard the whole board.
-	// Fall back to an empty author instead so these issues still surface.
-	if (issue.updatedDate == null || issue.url == null) return undefined;
-
-	// Jira SDK results derive this category from a localized display name and default unknown names to DONE.
-	// Only the direct point read opts in because it maps Jira's stable status-category key itself.
-	const closed =
-		issue.closedDate != null ||
-		(issue.state?.category === 'DONE' &&
-			(provider.id !== IssuesCloudHostIntegrationId.Jira || options?.reliableStateCategory === true));
-
-	return {
-		type: 'issue',
-		provider: provider,
-		// `id` is the provider's display number/key (GitHub number, Jira/Linear key, Trello idShort), NOT a
-		// globally-unique id: it's rendered to users as `#{id}`, used to build branch names, and passed back
-		// to the provider as the `getIssue`/cache lookup key, all of which expect the number. `nodeId` is the
-		// provider-native stable id, but its uniqueness scope is provider-specific (Azure work-item ids are
-		// organization-scoped), so cross-scope consumers must include provider/domain/container identity too.
-		// provider-apis declares this as a string, but some providers (notably
-		// Azure's broadened work-item path) return a number at runtime. Keep the
-		// public IssueShape contract truthful for consumers that use string APIs.
-		id: toIssueIdentifier(issue.number),
-		nodeId: issue.graphQLId ?? issue.id,
-		title: issue.title,
-		url: issue.url,
-		createdDate: issue.createdDate,
-		updatedDate: issue.updatedDate,
-		closedDate: issue.closedDate ?? undefined,
-		closed: closed,
-		state: closed ? 'closed' : 'opened',
-		author: {
-			id: issue.author?.id ?? '',
-			// An absent name stays absent, matching {@link fromProviderAccount}; see `IssueMember.name`.
-			name: issue.author?.name ?? undefined,
-			avatarUrl: issue.author?.avatarUrl ?? undefined,
-			url: issue.author?.url ?? undefined,
-		},
-		assignees:
-			issue.assignees?.map(assignee => ({
-				id: assignee.id ?? '',
-				name: assignee.name ?? undefined,
-				avatarUrl: assignee.avatarUrl ?? undefined,
-				url: assignee.url ?? undefined,
-			})) ?? [],
-		project:
-			issue.project?.id && issue.project.resourceId && issue.project.namespace
-				? {
-						id: issue.project.id,
-						name: issue.project.name,
-						resourceId: issue.project.resourceId,
-						resourceName: issue.project.namespace,
-					}
-				: undefined,
-		repository:
-			issue.repository?.owner?.login != null
-				? {
-						owner: issue.repository.owner.login,
-						repo: issue.repository.name,
-						id: issue.repository.id,
-					}
-				: undefined,
-		labels: issue.labels.map(label => ({ color: label.color ?? undefined, name: label.name })),
-		commentsCount: issue.commentCount ?? undefined,
-		thumbsUpCount: issue.upvoteCount ?? undefined,
-		body: issue.description ?? undefined,
-		issueType: issue.type ?? undefined,
-	};
-}
-
-/**
- * Maps a raw provider-apis {@link ProviderRepository} to the GitLens-owned {@link ProviderRepositoryShape}
- * the ProviderBackend `listRepos` facade surfaces, so consumers don't depend on the SDK repo type. The SDK's
- * nullable fields (`webUrl`/`httpsUrl`/`sshUrl`/`defaultBranch`) collapse to `undefined`, matching the
- * `?? undefined` convention in {@link toIssueShape}/{@link toAccount}.
- */
-export function toProviderRepositoryShape(repo: ProviderRepository): ProviderRepositoryShape {
-	return {
-		id: repo.id,
-		namespace: repo.namespace,
-		name: repo.name,
-		project: repo.project ?? undefined,
-		url: repo.webUrl ?? undefined,
-		cloneUrlHttps: repo.httpsUrl ?? undefined,
-		cloneUrlSsh: repo.sshUrl ?? undefined,
-		defaultBranch: repo.defaultBranch?.name ?? undefined,
-	};
-}
-
-export function issueFilterToReason(filter: IssueFilter): 'authored' | 'assigned' | 'mentioned' {
-	switch (filter) {
-		case IssueFilter.Author:
-			return 'authored';
-		case IssueFilter.Assignee:
-			return 'assigned';
-		case IssueFilter.Mention:
-			return 'mentioned';
-	}
-}
-
-export function toAccount(account: ProviderAccount, provider: ProviderReference): UserAccount {
-	return {
-		provider: provider,
-		id: account.id,
-		name: account.name ?? undefined,
-		email: account.email ?? undefined,
-		avatarUrl: account.avatarUrl ?? undefined,
-		username: account.username ?? undefined,
-	};
-}
-
-export const toProviderBuildStatusState = {
-	[PullRequestStatusCheckRollupState.Success]: GitBuildStatusState.Success,
-	[PullRequestStatusCheckRollupState.Failed]: GitBuildStatusState.Failed,
-	[PullRequestStatusCheckRollupState.Pending]: GitBuildStatusState.Pending,
-};
-
-export const fromProviderBuildStatusState = {
-	[GitBuildStatusState.Success]: PullRequestStatusCheckRollupState.Success,
-	[GitBuildStatusState.Failed]: PullRequestStatusCheckRollupState.Failed,
-	[GitBuildStatusState.Pending]: PullRequestStatusCheckRollupState.Pending,
-	[GitBuildStatusState.ActionRequired]: PullRequestStatusCheckRollupState.Failed,
-	// TODO: The rest of these are defaulted because we don't have a matching state for them
-	[GitBuildStatusState.Error]: undefined,
-	[GitBuildStatusState.Cancelled]: undefined,
-	[GitBuildStatusState.OptionalActionRequired]: undefined,
-	[GitBuildStatusState.Skipped]: undefined,
-	[GitBuildStatusState.Running]: undefined,
-	[GitBuildStatusState.Warning]: undefined,
-};
-
-/** Rolls every check context up into one state, the way a provider's own rollup does: failed, errored, or
- *  action-required fails; else pending or running is pending; else success — reading only the first context
- *  would call a pull request passing on the strength of whichever check happens to come back first. States
- *  carrying no verdict (cancelled, skipped, optional action required, warning) don't vote. Reads the raw
- *  state rather than `fromProviderBuildStatusState`, which drops errored and running to `undefined` and
- *  would let a lone success outvote a check still in flight. */
-function toStatusCheckRollupState(
-	statuses: GitBuildStatus[] | null | undefined,
-): PullRequestStatusCheckRollupState | undefined {
-	if (!statuses?.length) return undefined;
-
-	let rollup: PullRequestStatusCheckRollupState | undefined;
-	for (const { state } of statuses) {
-		switch (state) {
-			case GitBuildStatusState.Failed:
-			case GitBuildStatusState.Error:
-			case GitBuildStatusState.ActionRequired:
-				return PullRequestStatusCheckRollupState.Failed;
-			case GitBuildStatusState.Pending:
-			case GitBuildStatusState.Running:
-				rollup = PullRequestStatusCheckRollupState.Pending;
-				break;
-			case GitBuildStatusState.Success:
-				rollup ??= PullRequestStatusCheckRollupState.Success;
-				break;
-		}
-	}
-	return rollup;
-}
-
-export const toProviderPullRequestMergeableState = {
-	[PullRequestMergeableState.Mergeable]: GitPullRequestMergeableState.Mergeable,
-	[PullRequestMergeableState.Conflicting]: GitPullRequestMergeableState.Conflicts,
-	[PullRequestMergeableState.Unknown]: GitPullRequestMergeableState.Unknown,
-	[PullRequestMergeableState.FailingChecks]: GitPullRequestMergeableState.FailingChecks,
-	[PullRequestMergeableState.BlockedByPolicy]: GitPullRequestMergeableState.Blocked,
-};
-
-export const fromProviderPullRequestMergeableState = {
-	[GitPullRequestMergeableState.Mergeable]: PullRequestMergeableState.Mergeable,
-	[GitPullRequestMergeableState.Conflicts]: PullRequestMergeableState.Conflicting,
-	[GitPullRequestMergeableState.Blocked]: PullRequestMergeableState.BlockedByPolicy,
-	[GitPullRequestMergeableState.FailingChecks]: PullRequestMergeableState.FailingChecks,
-	[GitPullRequestMergeableState.Unknown]: PullRequestMergeableState.Unknown,
-	[GitPullRequestMergeableState.Behind]: PullRequestMergeableState.Unknown,
-	[GitPullRequestMergeableState.UnknownAndBlocked]: PullRequestMergeableState.Unknown,
-	[GitPullRequestMergeableState.Unstable]: PullRequestMergeableState.Unknown,
-};
-
-export function toProviderPullRequestState(state: PullRequestState): GitPullRequestState {
-	return state === 'opened'
-		? GitPullRequestState.Open
-		: state === 'closed'
-			? GitPullRequestState.Closed
-			: GitPullRequestState.Merged;
-}
-
-export function fromProviderPullRequestState(state: GitPullRequestState): PullRequestState {
-	return state === GitPullRequestState.Open ? 'opened' : state === GitPullRequestState.Closed ? 'closed' : 'merged';
-}
-
-type PullRequestStateInput = PullRequestState | PullRequestStateFilter;
-
-function toProviderPullRequestStatesCore(state: PullRequestStateInput): GitPullRequestState[] {
-	switch (state) {
-		case 'open':
-		case 'opened':
-			return [GitPullRequestState.Open];
-		case 'closed':
-			return [GitPullRequestState.Closed];
-		case 'merged':
-			return [GitPullRequestState.Merged];
-		case 'all':
-			return [GitPullRequestState.Open, GitPullRequestState.Closed, GitPullRequestState.Merged];
-	}
-}
-
-/** Maps PR include/state filters to the SDK's `states` input. `undefined`/omitted preserves the open-only default. */
-export function toProviderPullRequestStates(
-	state: PullRequestStateInput | PullRequestStateInput[] | undefined,
-): GitPullRequestState[] | undefined {
-	if (state == null) return undefined;
-
-	const states = (Array.isArray(state) ? state : [state]).flatMap(s => toProviderPullRequestStatesCore(s));
-	return states.length > 0 ? [...new Set(states)] : undefined;
-}
-
-/** Maps an issue state filter to the SDK's `states` input. `undefined`/omitted preserves the open-only default. */
-export function toProviderIssueStates(state: IssueStateFilter | undefined): GitIssueState[] | undefined {
-	switch (state) {
-		case 'open':
-			return [GitIssueState.Open];
-		case 'closed':
-			return [GitIssueState.Closed];
-		case 'all':
-			return [GitIssueState.Open, GitIssueState.Closed];
-		default:
-			return undefined;
-	}
-}
-
-/**
- * Resolves a normalized {@link ProviderScope} to the provider-appropriate read inputs, dispatching on the
- * provider's {@link PagingMode} (the authoritative per-provider scoping selector). Project-mode providers
- * (Azure issues, Jira) produce `projectInputs` from `org` + `project`; repo/repos-mode providers produce a
- * repo `GetRepoInput[]` from `scope.repos` (carrying `project` where relevant, e.g. Azure). This is the
- * single public entry point consumers can use instead of hand-building the three underlying representations.
- */
-export function resolveProviderScope(
-	scope: ProviderScope,
-	pagingMode: PagingMode | undefined,
-): { reposInput?: GetRepoInput[]; projectInputs?: { namespace: string; project: string }[] } {
-	if (pagingMode === PagingMode.Project) {
-		if (scope.org != null && scope.project != null) {
-			return { projectInputs: [{ namespace: scope.org, project: scope.project }] };
-		}
-		return {};
-	}
-
-	const reposInput = scope.repos?.map(r => ({ namespace: r.owner, name: r.name, project: scope.project }));
-	return { reposInput: reposInput };
-}
-
-export function providerPullRequestMatchesSearch(pr: ProviderPullRequest, search: string): boolean {
-	const term = search.trim().toLowerCase();
-	if (term.length === 0) return true;
-
-	return pr.title.toLowerCase().includes(term) || (pr.description?.toLowerCase().includes(term) ?? false);
-}
-
-function toProviderRemoteInfo(ref: PullRequestRef | undefined): GitRepositoryRemoteInfo | null {
-	// Match the SDK convention: only populate remoteInfo when both clone URLs are known.
-	return ref?.cloneHttps && ref?.cloneSsh ? { cloneUrlHTTPS: ref.cloneHttps, cloneUrlSSH: ref.cloneSsh } : null;
-}
-
-export function toProviderPullRequest(pr: PullRequest): ProviderPullRequest {
-	const prReviews = [...(pr.reviewRequests ?? []), ...(pr.latestReviews ?? [])];
-	return {
-		id: pr.id,
-		graphQLId: pr.nodeId,
-		number: pr.number ?? Number.parseInt(pr.id, 10),
-		title: pr.title,
-		description: pr.body ?? null,
-		url: pr.url,
-		state: toProviderPullRequestState(pr.state),
-		isCrossRepository: pr.refs?.isCrossRepository ?? false,
-		isDraft: pr.isDraft ?? false,
-		createdDate: pr.createdDate,
-		updatedDate: pr.updatedDate,
-		closedDate: pr.closedDate ?? null,
-		mergedDate: pr.mergedDate ?? null,
-		commentCount: pr.commentsCount ?? null,
-		upvoteCount: pr.thumbsUpCount ?? null,
-		commitCount: pr.commitCount ?? null,
-		fileCount: null,
-		additions: pr.additions ?? null,
-		deletions: pr.deletions ?? null,
-		author: toProviderAccount(pr.author),
-		assignees: pr.assignees?.map(toProviderAccount) ?? null,
-		baseRef:
-			pr.refs?.base == null
-				? null
-				: {
-						name: pr.refs.base.branch,
-						oid: pr.refs.base.sha,
-					},
-		headRef:
-			pr.refs?.head == null
-				? null
-				: {
-						name: pr.refs.head.branch,
-						oid: pr.refs.head.sha,
-					},
-		// `null` when the source carried no review data at all, rather than the empty array a lite read would
-		// otherwise produce: `toCompletedReviews`/`toReviewRequests` map `null` back to `undefined`, which is what
-		// lets a consumer tell "nobody has reviewed this" from "this read never fetched reviews" (see
-		// `PullRequestShape.latestReviews`). An empty array from a full projection stays an empty array.
-		reviews: pr.reviewRequests == null && pr.latestReviews == null ? null : toProviderReviews(prReviews),
-		reviewDecision: toProviderReviewDecision(pr.reviewDecision, prReviews),
-		repository:
-			pr.repository != null
-				? {
-						id: pr.repository.id ?? '',
-						name: pr.repository.repo,
-						owner: {
-							login: pr.repository.owner,
-						},
-						remoteInfo: toProviderRemoteInfo(pr.refs?.base),
-					}
-				: {
-						id: '',
-						name: '',
-						owner: {
-							login: '',
-						},
-						remoteInfo: null,
-					},
-		headRepository:
-			pr.refs?.head != null
-				? {
-						id: pr.refs.head.repo,
-						name: pr.refs.head.repo,
-						owner: {
-							login: pr.refs.head.owner,
-						},
-						remoteInfo: toProviderRemoteInfo(pr.refs.head),
-						isFork: pr.refs.head.isFork,
-					}
-				: null,
-		headCommit:
-			pr.statusCheckRollupState != null
-				? {
-						buildStatuses: [
-							{
-								completedAt: null,
-								description: '',
-								name: '',
-								state: toProviderBuildStatusState[pr.statusCheckRollupState],
-								startedAt: null,
-								stage: null,
-								url: '',
-							},
-						],
-					}
-				: null,
-		permissions:
-			pr.viewerCanUpdate == null
-				? null
-				: {
-						canMerge:
-							pr.viewerCanUpdate === true &&
-							pr.repository.accessLevel != null &&
-							pr.repository.accessLevel >= RepositoryAccessLevel.Write,
-						canMergeAndBypassProtections:
-							pr.viewerCanUpdate === true &&
-							pr.repository.accessLevel != null &&
-							pr.repository.accessLevel >= RepositoryAccessLevel.Admin,
-					},
-		mergeableState: pr.mergeableState
-			? toProviderPullRequestMergeableState[pr.mergeableState]
-			: GitPullRequestMergeableState.Unknown,
-	};
-}
-
-export function fromProviderPullRequest(
-	pr: ProviderPullRequest,
-	provider: Provider,
-	options?: { project?: IssueProject; currentAccountId?: string },
-): PullRequest {
-	const repository = pr.repository;
-	const repositoryName = repository?.name ?? '';
-	const repositoryOwner = repository?.owner?.login ?? '';
-	const repositoryRemoteInfo = repository?.remoteInfo;
-	const headRepository = pr.headRepository;
-	const headRepositoryRemoteInfo = headRepository?.remoteInfo;
-
-	return new PullRequest(
-		provider,
-		fromProviderAccount(pr.author),
-		pr.id,
-		pr.graphQLId || pr.id,
-		pr.title,
-		pr.url ?? '',
-		{
-			owner: repositoryOwner,
-			repo: repositoryName,
-			// This has to be here until we can take this information from ProviderPullRequest:
-			accessLevel: RepositoryAccessLevel.Write,
-			id: repository?.id ?? '',
-		},
-		fromProviderPullRequestState(pr.state),
-		pr.createdDate,
-		pr.updatedDate,
-		pr.closedDate ?? undefined,
-		pr.mergedDate ?? undefined,
-		pr.mergeableState ? fromProviderPullRequestMergeableState[pr.mergeableState] : undefined,
-		pr.permissions?.canMerge || pr.permissions?.canMergeAndBypassProtections ? true : undefined,
-		{
-			base: {
-				branch: pr.baseRef?.name ?? '',
-				sha: pr.baseRef?.oid ?? '',
-				repo: repositoryName,
-				owner: repositoryOwner,
-				exists: pr.baseRef != null,
-				url: repositoryRemoteInfo?.cloneUrlHTTPS
-					? repositoryRemoteInfo.cloneUrlHTTPS.replace(gitSuffixRegex, '')
-					: '',
-				cloneHttps: repositoryRemoteInfo?.cloneUrlHTTPS || undefined,
-				cloneSsh: repositoryRemoteInfo?.cloneUrlSSH || undefined,
-			},
-			head: {
-				branch: pr.headRef?.name ?? '',
-				sha: pr.headRef?.oid ?? '',
-				repo: headRepository?.name ?? '',
-				owner: headRepository?.owner?.login ?? '',
-				exists: pr.headRef != null,
-				url: headRepositoryRemoteInfo?.cloneUrlHTTPS
-					? headRepositoryRemoteInfo.cloneUrlHTTPS.replace(gitSuffixRegex, '')
-					: '',
-				cloneHttps: headRepositoryRemoteInfo?.cloneUrlHTTPS || undefined,
-				cloneSsh: headRepositoryRemoteInfo?.cloneUrlSSH || undefined,
-				isFork: headRepository?.isFork,
-			},
-			isCrossRepository: pr.isCrossRepository,
-		},
-		pr.isDraft,
-		pr.additions ?? undefined,
-		pr.deletions ?? undefined,
-		pr.commentCount ?? undefined,
-		pr.upvoteCount ?? undefined,
-		pr.reviewDecision ? fromPullRequestReviewDecision[pr.reviewDecision] : undefined,
-		toReviewRequests(pr.reviews),
-		toCompletedReviews(pr.reviews),
-		pr.assignees?.map(fromProviderAccount) ?? undefined,
-		toStatusCheckRollupState(pr.headCommit?.buildStatuses),
-		options?.project,
-		pr.version,
-		pr.commitCount ?? undefined,
-		undefined, // stack — GK's proxy type has no stack concept; membership is joined host-side
-		pr.fileCount ?? undefined,
-		pr.description ?? undefined,
-		pr.number,
-		options?.currentAccountId != null ? pr.author?.id === options.currentAccountId : undefined,
-	);
-}
-
-export function fromProviderIssue(
-	issue: ProviderIssue,
-	integration: Integration,
-	options?: { project?: IssueProject },
-): Issue {
-	const identifier = toIssueIdentifier(issue.number);
-	const closed = issue.closedDate != null || issue.state?.category === 'DONE';
-	return new Issue(
-		integration,
-		identifier,
-		issue.graphQLId ?? issue.id,
-		issue.title,
-		issue.url ?? '',
-		issue.createdDate,
-		issue.updatedDate ?? issue.closedDate ?? issue.createdDate,
-		closed,
-		closed ? 'closed' : 'opened',
-		fromProviderAccount(issue.author),
-		issue.assignees?.map(fromProviderAccount) ?? undefined,
-		issue.repository != null
-			? {
-					owner: issue.repository.owner.login ?? '',
-					repo: issue.repository.name,
-					id: issue.repository.id,
-				}
-			: undefined,
-		issue.closedDate ?? undefined,
-		issue.labels?.map(label => ({ name: label.name, color: label.color ?? undefined })),
-		issue.commentCount ?? undefined,
-		issue.upvoteCount ?? undefined,
-		issue.description ?? undefined,
-		options?.project != null
-			? {
-					id: options.project.id,
-					name: options.project.name,
-					resourceId: options.project.resourceId,
-					resourceName: options.project.resourceName,
-				}
-			: issue.project?.id && issue.project?.resourceId && issue.project?.namespace
-				? {
-						id: issue.project.id,
-						name: issue.project.name,
-						resourceId: issue.project.resourceId,
-						resourceName: issue.project.namespace,
-					}
-				: undefined,
-		identifier,
-		issue.type ?? undefined,
-	);
-}
-
-export function toProviderPullRequestWithUniqueId(pr: PullRequest): PullRequestWithUniqueID {
-	const { reviews, ...providerPr } = toProviderPullRequest(pr);
-	return {
-		...providerPr,
-		// The SDK boundary: `getActionablePullRequests` categorizes by review state and only knows
-		// provider-apis' own vocabulary, so the locally-added dismissed state is dropped here rather than
-		// handed over as a value it would fall through on. Our own projection keeps it — see
-		// `providerPullRequestReviewStateDismissed`. `commitOid` rides along on the surviving reviews: it is an
-		// extra property the SDK ignores, not a value it could misread.
-		reviews:
-			reviews?.filter(
-				(r): r is ProviderPullRequestReview & { state: GitPullRequestReviewState } =>
-					r.state !== providerPullRequestReviewStateDismissed,
-			) ?? null,
-		uuid: EntityIdentifierUtils.encode(getEntityIdentifierInput(pr)),
-	};
-}
-
-export type ProviderActionablePullRequest = ActionablePullRequest;
-
-/**
- * Built on the SDK's `GitPullRequest`, NOT the local {@link ProviderPullRequest} widening: this is handed to
- * `getActionablePullRequests`, which categorizes by review state and only knows provider-apis' vocabulary.
- * {@link toProviderPullRequestWithUniqueId} is what narrows `reviews` down to it.
- */
-export type EnrichablePullRequest = GitPullRequest & {
-	uuid: string;
-	type: 'pullrequest';
-	provider: ProviderReference;
-	enrichable: EnrichableItem;
-	repoIdentity: PullRequestRepositoryIdentityDescriptor;
-	refs?: PullRequestRefs;
-	underlyingPullRequest: PullRequest;
-};
-
-export const getActionablePullRequests = GitProviderUtils.getActionablePullRequests;
-
-export type GitConfigEntityIdentifier = AnyEntityIdentifierInput & {
-	metadata: {
-		id: string;
-		owner: { key: string; name: string; id: string | undefined; owner: string | undefined };
-		createdDate: string;
-		isCloudEnterprise?: boolean;
-	};
-};
-
-export function isGitHubDotCom(domain: string | null | undefined): boolean {
-	return equalsIgnoreCase(domain, 'github.com');
-}
-
-export function isGitLabDotCom(domain: string | null | undefined): boolean {
-	return equalsIgnoreCase(domain, 'gitlab.com');
-}
-
-// Anchor the `visualstudio.com` alternative on a label boundary (`^` or `.`) rather than `\b`: `\b` treats a
-// hyphen as a word boundary, so `\bvisualstudio\.com$` matched attacker-controlled hosts like
-// `evil-visualstudio.com` and classified them as Azure cloud, changing their auth/URL handling.
-const azureCloudDomainRegex = /^dev\.azure\.com$|(?:^|\.)visualstudio\.com$/i;
-export function isAzureCloudDomain(domain: string | undefined): boolean {
-	return domain != null && azureCloudDomainRegex.test(domain);
-}
-
-const bitbucketCloudDomainRegex = /^bitbucket\.org$/i;
-export function isBitbucketCloudDomain(domain: string | undefined): boolean {
-	return domain != null && bitbucketCloudDomainRegex.test(domain);
-}
-
-export function supportsCodeSuggest(provider: ProviderReference): boolean {
-	return isGitHubDotCom(provider.domain);
-}