/**
 * `agents artifacts setup` — configure the artifact share endpoint (Cloudflare
 * R2 + Worker) that backs `agents artifacts share`.
 *
 * One door, two modes, because it replaces two commands that used to be
 * separate (RUSH-2580): the interactive wizard formerly at `agents setup share`
 * and the flag-driven provisioner formerly at `agents share setup`. On a TTY
 * with no provisioning flags TYPED it runs the wizard (provision or join, and
 * offers a Worker update when an endpoint already exists); with any provisioning
 * flag typed, or on a non-TTY, it provisions directly. Both modes call the same
 * `runShareProvision` / `runShareJoin` in commands/share.ts, so there is a
 * single source of truth for provisioning.
 *
 * "Typed", not "present", is load-bearing — see {@link isDirectProvisionRequest}.
 *
 * Idempotent: re-running shows the current endpoint and offers to reconfigure.
 */
import type { Command } from 'commander';
/**
 * Interactive share setup. Returns true if the user configured (or already had)
 * an endpoint, false if they skipped. Never throws on user cancel — callers
 * (the `agents setup` hub) rely on that to keep the fresh-machine flow going.
 */
export declare function runShareWizard(): Promise<boolean>;
/** Parsed `agents artifacts setup` options — the retired `agents share setup` flag set. */
interface ArtifactsSetupOpts {
    bundle: string;
    worker: string;
    bucket: string;
    account?: string;
    token?: string;
    domain?: string;
    analyticsToken?: string;
}
/** The provisioning flags, by their commander option-value keys. */
declare const PROVISION_FLAGS: readonly ["bundle", "worker", "bucket", "account", "token", "domain", "analyticsToken"];
/**
 * True when the invocation named a Cloudflare endpoint detail, i.e. the caller
 * is driving the old `agents share setup` provisioning path rather than asking
 * for the wizard.
 *
 * `--bundle`/`--worker`/`--bucket` carry commander defaults, so their mere
 * PRESENCE proves nothing — the question is whether the user typed them, which
 * only `wasTyped` (backed by commander's `getOptionValueSource`) can answer.
 * Reading presence alone would classify `agents artifacts setup --bundle
 * cloudflare-work` as a wizard run and then silently provision against the
 * DEFAULT bundle, i.e. someone else's Cloudflare account. The other four flags
 * have no default, so presence is proof for them.
 */
export declare function isDirectProvisionRequest(opts: ArtifactsSetupOpts, wasTyped?: (flag: (typeof PROVISION_FLAGS)[number]) => boolean): boolean;
/** Register `agents artifacts setup` under the parent `artifacts` command. */
export declare function registerArtifactsSetupCommand(artifactsCmd: Command): void;
export {};
