import { z } from "zod";
import type { McpTool } from "../tool.js";
declare const inputSchema: z.ZodObject<{
    path: z.ZodString;
    /** Project slug. Optional — defaults to the sentinel "default" project,
     *  the same Phase 1D-friendly fallback that ingest_content uses. */
    project: z.ZodDefault<z.ZodString>;
    /**
     * Optional override. When omitted, `type` is inferred from the file
     * extension (see EXT_TO_TYPE below).
     */
    type: z.ZodOptional<z.ZodEnum<["doc", "code", "meeting", "conversation", "note", "decision", "brief", "digest"]>>;
    title: z.ZodDefault<z.ZodString>;
    tags: z.ZodDefault<z.ZodArray<z.ZodString, "many">>;
    /** Fail fast if the file is bigger than this many bytes. Default 5 MiB
     *  — covers most text files comfortably and is large enough for typical
     *  PDFs (technical docs, contracts) without forcing the caller to
     *  override. Bump explicitly for large PDFs / books. */
    maxBytes: z.ZodDefault<z.ZodNumber>;
}, "strip", z.ZodTypeAny, {
    project: string;
    path: string;
    title: string;
    tags: string[];
    maxBytes: number;
    type?: "brief" | "code" | "meeting" | "decision" | "doc" | "note" | "digest" | "conversation" | undefined;
}, {
    path: string;
    project?: string | undefined;
    type?: "brief" | "code" | "meeting" | "decision" | "doc" | "note" | "digest" | "conversation" | undefined;
    title?: string | undefined;
    tags?: string[] | undefined;
    maxBytes?: number | undefined;
}>;
interface Output {
    ingested: number;
    sourceId: string;
    project: string;
    type: string;
    bytes: number;
    memories: Array<{
        content_preview: string;
        source_id: string;
        title?: string;
    }>;
    /**
     * Per-memory failures from the inner pipeline. Mirrors the
     * `errors` field on `ingest_content.handler` — forwarded here
     * so ingest_file callers see the same partial-success picture.
     */
    errors: Array<{
        source_id: string;
        error: string;
    }>;
}
/**
 * Read a file from the cortex process's filesystem and ingest it.
 *
 * Works when cortex can see the file — typical for `cortex start` on
 * the same host as the file. In a Docker deployment, the path must
 * resolve inside the container; bind-mount the source dir into the
 * compose file or prefer `ingest_content` where Claude does the read.
 */
export declare const ingestFile: McpTool<typeof inputSchema, Output>;
export {};
//# sourceMappingURL=ingest-file.d.ts.map