/**
 * HTTP client for the `configs.push` oRPC procedure (qfg-azk.13).
 *
 * Server-side spec lives at
 * `app-quonfig/src/lib/orpc/routes/config-push-handler.ts`. We translate the
 * oRPC error shape into a tagged union the CLI can pattern-match on:
 *
 *   - 200 → `{kind: 'success', commitSha}`
 *   - 403 with `data.denials` → `{kind: 'denied', denials}`
 *   - 409 → `{kind: 'conflict', message}`
 *   - 400 → `{kind: 'bad-request', message}`
 *   - anything else → throws so runPush surfaces a generic PushFatalError.
 *
 * The auth header is a WorkOS access token (or a `qf_uk_*` user key /
 * `qf_sa_*` service-account key when `QUONFIG_API_KEY` is set in the
 * environment); see `getValidAccessToken`.
 */
import type { ConfigPushInput, ConfigPushResult, GitPushInput, GitPushResult } from './run-push.js';
export declare const callConfigsPush: (input: ConfigPushInput, orgSlug: string) => Promise<ConfigPushResult>;
/**
 * Pack-push wire client for `configs.gitPush` (qfg-7429.4). Mirrors
 * `callConfigsPush` shape — same oRPC `{json: ...}` envelope, same
 * status-to-tagged-union mapping. Two differences:
 *
 *   - The pack is base64-encoded so the JSON envelope stays text-safe;
 *     the server-side handler (`git-push-handler.ts`) decodes it via
 *     `Buffer.from(input.pack, 'base64')`.
 *   - 403 denials carry `{commitSha, path, reason, requiredPermission}`
 *     plus an optional `suggestedRecovery` block for the GitHub-fork
 *     dead-end UX (see §6 of the design plan and qfg-7429.5 for the
 *     polished renderer).
 */
export declare const callConfigsGitPush: (input: GitPushInput, orgSlug: string) => Promise<GitPushResult>;