/**
 * The Cloud-project half of the OAuth path: gcloud and the console pages.
 *
 * Split out of `setup-actions.ts` because it answers a different question. That
 * module binds step ids to runners and owns the consent exchange; these six
 * steps are about the PROJECT the OAuth client will live in, is gcloud there,
 * is it signed in, which project, which APIs, is the consent screen filled in,
 * is the app published. None of it runs on a machine that already has a client,
 * which is the whole point of the `existing-client` path.
 *
 * Every one of these is scriptable through gcloud except the two Google exposes
 * no API for: the consent screen and the audience/publishing setting. Those two
 * report `needs-human` and say exactly what to click.
 */
import type { GoogleStepRunner } from './setup-flow.js';
import type { GoogleStepId } from './types.js';
import type { GoogleSetupActionDeps } from './setup-action-deps.js';
/** Turn whichever intake route was chosen into client credentials. */
/**
 * Bind the six project-and-console steps.
 *
 * The `GcloudState` is created here and shared across them, so the executable
 * that answered `--version` is the one every later call uses rather than each
 * step re-detecting it.
 */
export declare function buildCloudProjectRunners(deps: GoogleSetupActionDeps): ReadonlyMap<GoogleStepId, GoogleStepRunner>;
//# sourceMappingURL=setup-actions-cloud-project.d.ts.map