import type { FrameworkBuilder } from "../../types/frameworkBuilder.js";
/**
 * The warning for a docker-claimed app whose plan runs NOTHING at build time
 * (no Dockerfile, so no image build; the catch-all never has a build
 * command). Returned by {@link dockerNoBuildStepWarning} and emitted on the
 * deploy's warning lane.
 *
 * The lane itself stays fully supported — DevOps users composing raw
 * factories (e.g. StorageFactory + CdnFactory as a hand-composed static
 * site) is a documented break-out path, not an error. What was silent, and
 * must not be, is that nothing runs their site's build: a deploy after an
 * edit ships whatever bytes are already on disk, which reads as "deploy
 * succeeded but my change isn't live".
 */
export declare const NO_BUILD_STEP_WARNING: string;
/**
 * The no-op-build tripwire: returns {@link NO_BUILD_STEP_WARNING} when the
 * docker catch-all claimed the app and its plan carries no build work of any
 * kind — no Docker image build, no build command, no pre-build commands.
 * Scoped to the docker claim: the staticsite builder can also plan a null
 * buildCommand (unreadable build inputs), but its `build()` then fails
 * loudly, and a warning in front of that error would be noise.
 */
export declare function dockerNoBuildStepWarning(plan: {
    readonly builderName: string;
    readonly buildCommand: unknown;
    readonly preBuildCommands: readonly unknown[];
    readonly requiresDockerBuild: boolean;
}): string | undefined;
/**
 * Docker FrameworkBuilder for standard containerised applications.
 *
 * Priority 100 — checked last as the fallback builder. Any Fjall app with
 * an infrastructure.ts file is a valid Docker app unless a higher-priority
 * builder (e.g. OpenNext) claims it first.
 */
export declare const dockerBuilder: FrameworkBuilder;