/**
 * Positional tokens after `rebase cloud` (group, action, …).
 *
 * Two things stop a flag being mistaken for the group. `GLOBAL_CLOUD_FLAGS` is
 * declared so `arg` *consumes* the flags that may precede it — critically
 * together with their values, which is the half that filtering cannot do. The
 * leading-`-` skip then covers a flag nobody declared, so an unrecognised
 * boolean shifts nothing.
 *
 * Only leading tokens are skipped: past the group and action, an undeclared
 * flag and its value are somebody else's positionals and none of our business.
 * A flag this file has never heard of, that takes a value, placed before the
 * group, is the one shape still unresolvable here — there is no way to know
 * whether the token after it is its value or the group, and guessing either way
 * is worse than the handler reporting an unknown group.
 *
 * Exported so its tests can drive the real thing. The dispatch test used to
 * re-implement it locally as `slice(3).filter(a => !a.startsWith("-"))` — which
 * filtered flags, while this function did not — so the test asserted the
 * behaviour we wanted against a copy that had it, and stayed green for as long
 * as the real dispatcher was broken.
 */
export declare function positionals(rawArgs: string[]): string[];
export declare function cloudCommand(subcommand: string | undefined, rawArgs: string[]): Promise<void>;