import { Editor, SuperDocExceptionDiagnosticPayload } from '../../core/types/index.js';
type DiagnosticTranslationContext = {
    documentId?: string | null;
    editor?: Editor | null;
};
type DiagnosticRecord = {
    code?: string;
    severity?: string;
    message?: string;
};
type RenderReadinessDiagnostic = {
    code?: string;
    reason?: string;
    severity?: string;
    error?: {
        name?: unknown;
        message?: unknown;
        stack?: unknown;
    };
};
/**
 * Translates a `SDDiagnosticRecord`-shaped object (package-open / unzip
 * stage) into a public diagnostic payload, or `null` if out of scope.
 */
export declare function translateUnzipDiagnostic(record: DiagnosticRecord | null | undefined, ctx?: DiagnosticTranslationContext): SuperDocExceptionDiagnosticPayload | null;
/**
 * Translates a `V2RenderReadinessDiagnostic`-shaped object (render stage)
 * into a public diagnostic payload, or `null` if out of scope.
 */
export declare function translateRenderReadinessDiagnostic(diag: RenderReadinessDiagnostic | null | undefined, ctx?: DiagnosticTranslationContext): (SuperDocExceptionDiagnosticPayload & {
    error: Error;
}) | null;
/**
 * Translates a boot/open failure into a public diagnostic payload, or
 * `null` if out of scope.
 *
 * `bootErrorName`, when present, takes precedence over `reason` — several
 * `boot()` catch sites in `V2SuperEditor.vue` hardcode `reason: 'open-failed'`
 * regardless of which error was actually thrown, so `reason` alone is not a
 * reliable signal once a real caught-error name is available.
 */
export declare function translateBootFailureReason(reason: string, detail?: string | null, ctx?: DiagnosticTranslationContext & {
    bootErrorName?: string;
}): SuperDocExceptionDiagnosticPayload | null;
/**
 * Translates a `SDDiagnosticRecord`-shaped source-signals diagnostic (parse
 * stage) into a public diagnostic payload, or `null` if out of scope.
 *
 * `error`-severity only, unlike `translateUnzipDiagnostic`'s allow-listed
 * warns: every `*-parse-error` code in `SSIG_PARSE_ERROR_CODES` is also
 * emitted at `warn` for soft/summary conditions that are NOT a genuine parse
 * failure -- e.g. `SSIG-SETTINGS-parse-error` warns on a missing-but-optional
 * settings part (settings-signals.ts), `SSIG-SECT-parse-error` warns as a
 * chunk-scan summary flag ("chunk scan reported diagnostics") rather than a
 * specific failure (signal-builder.ts), and `SSIG-USAGE-body-parse-error`/
 * `SSIG-USAGE-numbering-parse-error` are warn-only in every producer site --
 * no vetted warn case among the 5 codes represents a real parse failure, so
 * unlike the unzip translator's `main-document-fallback` there is nothing to
 * allow-list here.
 */
export declare function translateSsigParseDiagnostic(record: DiagnosticRecord | null | undefined, ctx?: DiagnosticTranslationContext): SuperDocExceptionDiagnosticPayload | null;
/**
 * Translates a DOCX export failure (a plain caught `Error`/`unknown` -- no
 * internal taxonomy exists at this layer to duck-type on) into a public
 * diagnostic payload. Always returns a payload; export failures always
 * classify as `RENDER_ERROR`/`'export'` -- a serialization failure of an
 * already-open document, not a document-corruption or capacity issue.
 */
export declare function translateExportDiagnostic(error: unknown, ctx?: DiagnosticTranslationContext): SuperDocExceptionDiagnosticPayload;
export {};