/**
 * Framework path validation and cached module integrity checks.
 *
 * Validates that cached module code has compatible file:// paths
 * for the current execution environment.
 *
 * @module transforms/mdx/esm-module-loader/module-fetcher/framework-validator
 */
import type { Logger } from "../../../../utils/index.js";
interface MdxRecoveryOptions {
    projectId: string;
    contentSourceId: string;
}
/**
 * Check if cached code has file:// paths that are incompatible with this environment.
 * Returns true if the cached code should be invalidated (has paths from a different environment).
 *
 * Checks for:
 * 1. Framework source paths (file:///app/src/...) that don't match FRAMEWORK_ROOT
 * 2. HTTP bundle cache paths (file:///app/.cache/veryfront-http-bundle/...) that don't match local cache dir
 * 3. MDX ESM cache paths (file:///app/.cache/veryfront-mdx-esm/...) that don't match local cache dir
 *
 * This check also walks transitively imported VF modules so nested stale paths
 * are rejected before import-time failures.
 */
export declare function hasIncompatibleFrameworkPaths(code: string, log: Logger): Promise<boolean>;
/**
 * Check if cached code has file:// paths that don't exist locally.
 * Returns list of missing paths, or empty array if all exist.
 *
 * This catches cases where distributed cache returns code with file:// paths
 * to vfmod modules that were created on a different pod/run with different hashes.
 */
export declare function findMissingFileDependenciesInCode(code: string, log: Logger): Promise<string[]>;
export declare function validateCachedModule(normalizedPath: string, cachedPath: string, cachedCode: string, log: Logger, pathCache: Map<string, string>, versionedKey: string, recoveryOptions?: MdxRecoveryOptions): Promise<boolean>;
export {};
//# sourceMappingURL=framework-validator.d.ts.map