import { z } from "zod";
import type { McpTool } from "../tool.js";
declare const inputSchema: z.ZodObject<{
    /** Job id returned by the originating async handler. */
    jobId: z.ZodString;
}, "strip", z.ZodTypeAny, {
    jobId: string;
}, {
    jobId: string;
}>;
interface Output {
    /** True when the registry knew the jobId. */
    found: boolean;
    jobId: string;
    /** queued / running / completed / failed; omitted when found=false. */
    status?: "queued" | "running" | "completed" | "failed";
    /** Free-form progress payload the handler updates mid-flight. Common
     *  shape: { totalUnits, doneUnits, message }. */
    progress?: Record<string, unknown>;
    /** Final payload on completed jobs (mirrors the synchronous return
     *  shape of the originating tool). */
    result?: unknown;
    /** Error message on failed jobs. */
    error?: string;
    /** ISO timestamps for the lifecycle. */
    createdAt?: string;
    startedAt?: string | null;
    finishedAt?: string | null;
}
/**
 * Poll an in-flight or recently-completed background job.
 *
 * The async-mode handlers (currently `ingest_repo` with `async: true`)
 * return `{ jobId, queued }` immediately and run the work in the
 * background; clients poll this to find out when the work finished
 * and what it produced. Completed / failed jobs are retained for 24
 * hours so a slow consumer can still fetch the result long after the
 * work landed.
 *
 * Unknown jobIds return `{ found: false }` rather than throwing —
 * lets pollers loop without special-casing the 'maybe expired'
 * branch.
 */
export declare const kbJobStatus: McpTool<typeof inputSchema, Output>;
export {};
//# sourceMappingURL=kb-job-status.d.ts.map