/**
 * Build-failure tagging for module loads.
 *
 * A page module can fail for two very different reasons, and callers need to
 * tell them apart:
 *
 * - The source could not be compiled or resolved. That is a developer-facing
 *   build failure, and the message says how to fix it.
 * - The module compiled, ran, and threw at module scope (a missing environment
 *   variable, a rejected top-level `await`). That is an ordinary application
 *   error, and a project's own error page should present it.
 *
 * Only the loader is in a position to know which happened, so it tags the
 * error at the point of failure instead of leaving later layers to infer it.
 */
/** Tag `error` as a build failure and return it. */
export declare function markBuildFailure(error: unknown): unknown;
/**
 * Tag `error` as a build failure the tenant's own source caused, and return it.
 *
 * For seams that know the provenance from control flow rather than from a
 * registry slug — an import specifier that still does not resolve after a full
 * rebuild, for instance, is a path the project authored.
 */
export declare function markTenantBuildFailure(error: unknown): unknown;
/** True when `error` was raised while compiling or resolving project source. */
export declare function isBuildFailure(error: unknown): boolean;
/** True only for a build failure explicitly classified as tenant source. */
export declare function isTenantBuildFailure(error: unknown): boolean;
//# sourceMappingURL=build-failure.d.ts.map