import { type AppError, type AppErrorCode } from "./app-error.js";
import type { SuggestedAction } from "@agentxm/registry-protocol/unstable/suggested-action";
export declare const BC: {
    readonly run: (cmd: string, description: string) => SuggestedAction;
    readonly do: (description: string) => SuggestedAction;
};
/**
 * The one result for being signed out.
 *
 * There are two states, so there is one way to report the first: signed out,
 * with the command that ends it. The device-code form is carried alongside for
 * an invocation that has no terminal of its own to run a browser sign-in from,
 * and a token for one that cannot sign in at all. Nothing that a signed-in
 * person can hit renders this.
 */
export declare const errSignedOut: (message?: string, cause?: unknown) => AppError;
export declare const errPublishConflict: (args: {
    readonly version?: string;
    readonly cause?: unknown;
}) => AppError;
export declare const errInstallFailed: (args: {
    readonly message: string;
    readonly cause?: unknown;
}) => AppError;
export declare const errRegistryPublishRejected: (args: {
    readonly message: string;
    readonly suggestions?: ReadonlyArray<SuggestedAction>;
    readonly cause?: unknown;
}) => AppError;
/**
 * Change endpoint semantics on a mapped envelope while preserving failure
 * evidence and recovery. Owned here with the envelope vocabulary; the
 * registry integration's typed analogue is `withRegistrySemantics`.
 */
export declare const withAppErrorSemantics: (error: AppError, semantics: {
    readonly code?: AppErrorCode;
    readonly title?: string;
    readonly detail?: string;
    readonly suggestions?: ReadonlyArray<SuggestedAction>;
}) => AppError;
//# sourceMappingURL=builders.d.ts.map