/**
 * pop task submit — submit work for a claimed task.
 *
 * Order matters (fixed in the v6 migration): pre-flight runs FIRST, so a
 * submission that would revert (wrong status, not the claimer) fails fast
 * without wasting an IPFS pin. Then the pin, then the transaction.
 *
 * Expiry semantics (v6, verified against contracts origin/main): a lapsed
 * claim deadline NEVER blocks the original claimer's submitTask — it only
 * makes the task takeover-able by others until the submission lands. So an
 * expired claim is a WARNING here, not a failure.
 */
import type { Argv, ArgumentsCamelCase } from 'yargs';
interface SubmitArgs {
    org: string;
    task: string;
    submission: string;
    chain?: number;
    rpc?: string;
    'private-key'?: string;
    'dry-run'?: boolean;
    yes?: boolean;
    preflight?: boolean;
    commit?: boolean;
    commitFiles?: string;
    'idempotency-key'?: string;
    'no-idempotency'?: boolean;
}
export declare const submitHandler: {
    builder: (yargs: Argv) => Argv<{
        task: string;
    } & {
        submission: string;
    } & {
        commit: boolean;
    } & {
        "commit-files": string | undefined;
    } & {
        "idempotency-key": string | undefined;
    } & {
        "no-idempotency": boolean;
    }>;
    handler: (argv: ArgumentsCamelCase<SubmitArgs>) => Promise<void>;
};
export {};